fix(release): ensure given preid modifies conventional commits specifier

[JamesHenry]

Current Behavior

If a user passes --preid when using conventional commits it will not have any impact on the derived specifier. If they were to use an explicit --specifier to work around this, it would override the derived conventional commits specifier entirely which is not we they want.

Expected Behavior

If a user passes --preid and the resolved conventional commits specifier is not already a prerelease of some kind, modify the specifier dynamically to be a prerelease (which will later be combined with the given preid).

Example (after a breaking change to bar):

Related Issue(s)

Fixes #23235

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Jun 12, 2024 2:55pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f52e288. 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 6 targets

• nx affected --targets=e2e,e2e-ci --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=f52e2882bd7fc09ad4feb6dcc68f44b298579715 --parallel=1
• nx affected --targets=lint,test,build --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=f52e2882bd7fc09ad4feb6dcc68f44b298579715 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=f52e2882bd7fc09ad4feb6dcc68f44b298579715
• nx documentation --no-dte
• nx affected -t e2e-macos-ci --parallel=1 --base=4a5eb23302cc68ecedf2f4733f1e9aacfb14584e --head=f52e2882bd7fc09ad4feb6dcc68f44b298579715

---

Sent with 💌 from NxCloud.

Not sure about overall prerelease flow implications

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.