feat(inbound-filters): Add an issue action that drafts a custom filter from the event

[shellmayr]

• Adds "Add Inbound Filter" to the More Actions menu on issue details.
• Opens the custom filter modal with one condition per property the shown event has: exception type, exception message, country, release, IP address. The user removes the rows they do not want.
• Escapes event text as a Relay glob and folds line breaks into *. Raw exception type and message win over symbolicated ones.
• Shown only with inbound-filters-v2, inbound-filters-v2-ui, and inbound-filters-in-product-flows. Disabled without project write access, and disabled with "Your plan does not include custom inbound filters" when the project lacks the plan feature projects:custom-inbound-filters, like the discard item.
• Tracks the click as add_inbound_filter on the issue action analytics event.
• Based on ref(inbound-filters): Move the custom filter modal into its own module #126852 (modal move) and lands after it and after feat(inbound-filters): Register the inbound-filters-in-product-flows flag #126851 (flag). Rollout for the test orgs is getsentry/sentry-options-automatorref(app-platform): Move feature flagging into decorators #10091.

Closes TET-3107

[github-actions]

📊 Type Coverage Diff

Metric	Before	After	Delta
Coverage	95.69%	95.69%	±0%
Typed	142,391	142,416	🟢 +25
Untyped	6,415	6,416	🔴 +1

🔍 1 new type safety issue introduced

Type assertions (as) (1 new)

File	Line	Detail
static/app/views/settings/project/projectFilters/customFilterModal.tsx	437	as string[] — [...new Set(values.map(value => value?.trim()).filter(Boolean))] as string[]

This is informational only and does not block the PR.

[linear-code]

TET-3107