Allow locking a project to semver release ordering

Sentry automatically decides per project whether to compare releases by semver or by release order, based on its most recent releases. A few non-semver releases can silently flip a semver project to release-order comparison, and users have no way to opt out. This requests an explicit project-level option to always use semver ordering. Current behavior • follows_semver_versioning_scheme (src/sentry/models/release.py) checks the 10 most recent open releases by date_added, cached for 1 hour. With 10+ releases, at least 1 of the newest 3 and at least 3 of the newest 10 must be semver ([docs]( • If a short burst of non-semver releases makes up the newest 3 (e.g. auto-created from telemetry or created by another pipeline), the project is treated as release-order until semver releases catch up. • Regression detection then compares release dates instead of versions. An issue resolved after [email protected] regresses on an event from [email protected] if 0.3.0 was created more recently. Th…