Support org-wide error volume alerts across all projects

Orgs with many projects have no way to set a single alert that fires when any error—across all projects—exceeds a volume threshold (e.g., >10K occurrences/day). Alerts must be configured per project today, which also means new projects created after setup are not covered.

Current behavior

• Error volume alerts are scoped to a specific project at creation time
• No "all projects" or org-level scope exists for issue alert rules
• Projects created after an alert is configured are not automatically included

Gap

• A single "runaway" error in any project can consume significant quota before anyone notices
• Orgs that spin up new projects regularly have a persistent blind spot: new projects start unmonitored
• The only workaround is manually duplicating alert rules for every project, including retroactively adding new ones

Proposed capability
Support an org-wide alert scope (e.g., all projects — including future) on issue alert rules, so a single rule can fire when any error in any project exceeds a configurable occurrence threshold within a time window.

Start by locating the existing project-scoped issue alert rule configuration and evaluation flow, then trace how project creation and alert scope are represented. Done means an org-level rule can cover current and future projects and trigger on the stated occurrence threshold within a time window.