Sentry Issue Based Alerting for `cron` category can no longer distinguish between missed check-in and cron failure.

### Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

### Steps to Reproduce

Looks like the Cron Issue message does not contain info on the failure reason (whether corn failure was form missed check-in or some other failure). Instead, it has a generic `Your monitor has reached its failure threshold` message for all failure scenarios.

In the recent past, we could create Issue based alerts that targeted only missed checkins (or skipped on missed checkins) like this.

The only place in the issues page where I can see the info on the failure type is under `Evidence` section. But that data is not searchable via issue alert filter.

Which seems to get fetched via the `api/0/organizations//issues//events/recommended/?collapse=fullRelease` endpoint.

Could we either add that info back in the Cron issue message, or add support for filtering on the `Evidence` fields in the Cron issue related alerting.

### Expected Result

The issue based alert described above should filter for and alert on new `missed check-in` Issues created by the cron monitors.

### Actual Result

Does not alert on missed check-in` anymore.

### Product Area

Crons

### Link

_No response_

### DSN

_No response_

### Version

25.7.0

Reproduce the Cron issue alert behavior in self-hosted Sentry 25.7.0, focusing on how missed check-in and other cron failures produce their issue messages. Inspect the /api/0/organizations//issues//events/recommended/?collapse=fullRelease endpoint and the Evidence fields. Done means issue-based alerts can target newly created missed check-in issues again, either through the message or Evidence filtering.

Written by the indexing model from the issue text.