chore: migrate from semver to nx release

[NachoVazquez]

PR Checklist

Please check if your PR fulfills the following requirements:

• [x] The commit message follows our guidelines: CONTRIBUTING.md#commit
• [ ] Tests for the changes have been added (for bug fixes / features)
• [ ] Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

We are using the amazing @jsclutery/semver nx plugin to manage our releases.

What is the new behavior?

We are migrating to the native nx release functionality.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

This PR is blocked by https://github.com/nrwl/nx/issues/26241

[nx-cloud[bot]]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 034f2c92a9ed4d4a2c7666cf06eb3fcae2d7effe. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 2 targets

- [`nx affected -t lint test build e2e`](https://cloud.nx.app/runs/OGqbgbW2F6?utm_source=pull-request&utm_medium=comment) - [`nx-cloud record -- nx format:check`](https://cloud.nx.app/runs/2OvGu5vXoz?utm_source=pull-request&utm_medium=comment)

---

Sent with 💌 from NxCloud.