Archived issues still trigger alerts

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. Create an alert that triggers ie. when an event arrives in Sentry
2. Send a test event to trigger the alert
3. Archive the resulting issue until a specific date
4. Wait for the interval period to be over and then send the same test event again

### Expected Result

The second test event does not trigger the alert.

### Actual Result

The second test event still triggers the alert, even though the corresponding issue is archived.

Example alert rule from a support test org [here](https://kismeow.sentry.io/alerts/rules/javascript-rea/15973830/details/) and corresponding issue [here](https://kismeow.sentry.io/issues/6066674569/?project=4505244102426624&query=is%3Aarchived&referrer=issue-stream&stream_index=0).

Original ticket on Zendesk [here](https://sentry.zendesk.com/agent/tickets/151800).

### Product Area

Alerts

### Link

_No response_

### DSN

_No response_

### Version

_No response_

Reproduce the behavior using the alert rule and corresponding issue linked in the report: trigger an event, archive the issue until a specified date, then send the same event after the interval. Trace how alert evaluation handles the archived issue, and consider the work done when the second event no longer triggers the alert.

Written by the indexing model from the issue text.