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. <img width="1032" height="458" alt="Image" src="https://github.com/user-attachments/assets/71d48ff6-4f3e-4c63-a2cb-e41be478e640" /> 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. <img width="517" height="176" alt="Image" src="https://github.com/user-attachments/assets/2a5023c3-ac81-4421-be03-1b70251bb674" /> Which seems to get fetched via the `api/0/organizations/<org name>/issues/<id>/events/recommended/?collapse=fullRelease` endpoint. <img width="485" height="591" alt="Image" src="https://github.com/user-attachments/assets/2e1fab9e-0ad8-4d90-959a-a9d35fc311a3" /> 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