feat(autopilot): POC UI for instrumentation issues

[ArthurKnaus]

Add a separate issues list for instrumentation issues using existing utils and components in the issues codebase.

Note: This UI implementation is experimental and minimalistic. It enables us to test autopilot use-cases end-to-end before refining the details.

All changes are guarded by the feature flag organizations:seer-autopilot

[sentry]

Bug: The new IssueCategory.INSTRUMENTATION is not included in the VALID_ISSUE_CATEGORIES array, preventing its use in issue search filters and alert rules.
_{Severity: HIGH}

Suggested Fix

Add IssueCategory.INSTRUMENTATION to the VALID_ISSUE_CATEGORIES array in static/app/types/group.tsx to make the category available for searching and alerting.

Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: static/app/types/group.tsx#L108

Potential issue: The `IssueCategory.INSTRUMENTATION` enum member is defined but has been
omitted from the `VALID_ISSUE_CATEGORIES` array in `static/app/types/group.tsx`. This
omission prevents the new "instrumentation" category from being used in key product
areas. Specifically, users will be unable to filter for instrumentation issues via the
issue search UI, as `SEARCHABLE_ISSUE_CATEGORIES` is derived from this array.
Additionally, it will be impossible to create alert rules that trigger on the
`INSTRUMENTATION` category, as the rule configuration UI validates against the same
array. This undermines the utility of the new instrumentation issue page.

_{Did we get this right? 👍 / 👎 to inform future reviews.}