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.

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_

Start by tracing the Issues workflow for “Resolve in current release” and the release:latest selection behavior described in the report. Compare how each determines the current release, then add coverage for releases created out of semantic-version order. Done means resolution uses the latest semantic version rather than creation time.

Written by the indexing model from the issue text.