feat(releases): allow projects to pin semver ordering

[sansynx]

Summary

Related to #126295

Three recent non-semver releases can switch a project back to release-order comparison. An older semantic version created later can then reopen an issue that was already resolved

This adds an opt-in semver field to the project API, backed by sentry:semver and gated by organizations:project-semver-ordering. When enabled, valid semantic releases keep semantic ordering regardless of recent release names. The preference is checked before the heuristic cache, so changing it takes effect immediately

Automatic detection remains the default. Non-semver release versions still use the existing release-order fallback. Projects can turn the setting off even after the feature flag is disabled

This PR contains the backend change only. A settings-page toggle should follow separately under the repository's backend/frontend deployment rules. Feature rollout is not included

Validation

The backend workflow passed on c31afede, including all 22 backend test shards, API docs tests, migrations, and typing. GitHub pre-commit lint and both Sentry and Cursor reviews also passed on this revision

Ruff lint and format checks passed locally for all ten PR files, and git diff --check passed. The regression test was verified to fail before the original fix

Local pytest could not be rerun after the upstream merge because its container environment was unavailable. The local prek attempt timed out; GitHub's pre-commit job completed successfully

The optional OpenAPI comparison reports the expected semver additions against the production schema. Vercel requires Sentry team authorization. Downstream getsentry tests require a collaborator to add the Trigger: getsentry tests label after reviewing the code

AI assistance was used for implementation, review, and running the checks listed above

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[sansynx]

could a collaborator add the Trigger: getsentry tests label after reviewing this and authorize the Vercel preview? those checks are waiting on approval