Alerts - Issue alert -Add issue.id filtering to Alert Rules

### Problem Statement

Sentry alert rules currently lack the ability to filter by specific issue IDs. This creates significant challenges for teams who want to set up user-impact-based alerting while excluding known, non-critical issues that frequently meet the alert criteria.
Current limitations:
- No way to exclude specific issue IDs from triggering alerts
- Teams must manually archive issues to prevent alert fatigue
- Workarounds like custom tags require manual setup and maintenance
- High-volume applications struggle with signal-to-noise ratio in alerting

### Solution Brainstorm

Add issue.id as Event Attribute Filter
Add issue.id to the event attribute dropdown in alert rule editor
Support standard match types: equals, not equals, in, not in
Allow comma-separated values for excluding multiple issue IDs
Example: "The event's issue.id value not in 12345,67890,11111"
Alternative:
Group-level filtering: Add group_id as a filterable attribute

### Product Area

Alerts

Start with the Alerts product area and the alert rule editor, then trace how event attribute filters and match types are defined. The issue proposes filtering on issue.id with equals, not equals, in, and not in, but leaves the group_id alternative unresolved; done would require a decided scope and corresponding behavior for excluding selected issue IDs.

Written by the indexing model from the issue text.