Incorrect release date comparison for semver versions when unresolving issues

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

It's not clear how reproducible it is, but here is what we observed in this instance:

1. Mark some issue as resolved in a particular version (semver)
2. Later, have an older version (by semver) but newer (by creation date) report that exception
3. Observe that Sentry compares the releases by release date and unresolves the issue (and linked tickets)

More links available in the linked internal customer case

### Expected Result

Sentry should have compared this by semantic versioning

### Actual Result

Sentry compared by release creation date


### Product Area

Unknown

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Start from the issue-unresolution path described in the reproduction steps and trace how semantic versions and release creation dates are compared. Done means an older semver release cannot unresolve an issue merely because it was created later, with the behavior covered by a regression test.

Written by the indexing model from the issue text.