Resolve issue in current release does not respect semver order

### Environment SaaS (https://sentry.io/) ### Steps to Reproduce 1. Report releases to Sentry using semantic versioning 2. Have a release with "older" semantic version created after the current one 3. try to resolve an issue in the current release. ### Expected Result Resolve in current release to use latest release based on semantic versioning. ### Actual Result Resolve in current release uses the lasted created release based on creation time. See the screenshots, events found in Discover using "release:latest" follow semantic version as expected but the current release to resolve an issue uses the creation date. <img width="538" alt="Image" src="https://github.com/user-attachments/assets/5966dc5f-be8b-472d-97f6-6015ddeb8305" /> <img width="823" alt="Image" src="https://github.com/user-attachments/assets/4eacee69-0030-4422-aa01-d1cc529831e9" /> Issue reported in this [internal ticket. ](https://sentry.zendesk.com/agent/tickets/146345). ### Product Area Issues ### Link _No response_ ### DSN _No response_ ### Version _No response_