Resolved issues don't appear to check the release before regressing

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

We had a an issue come in on a production environment which is running version 3.25.47.21 and I marked the issue as resolved in the next release. I then deployed the next release (3.25.47.22) to the customer's UAT environment for their sign-off.

A little later the error occurred again on production and so it regressed the fix but it's still running the older version so it's not a regression.

### Expected Result

The error should instead have just been recorded as another event on the existing resolved issue and the status left unchanged.

### Actual Result

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Start in the Issues product area by tracing how a new event is compared with the release that resolved an issue. Reproduce the case where an event from an older release arrives after a newer release was deployed, and verify that it remains resolved rather than regressing; add or update coverage for that behavior.

Written by the indexing model from the issue text.