chore(top-issues): add pasting json to single card view

[cvxluo]

Add dev tool to paste json for the new top issues view

[sentry]

Bug: The handleParseJson function unsafely casts parsed JSON to ClusterSummary[] without validating object properties, leading to a crash when required properties are accessed later.
_{Severity: HIGH | Confidence: High}

🔍 Detailed Analysis

The handleParseJson function uses a type assertion as ClusterSummary[] on user-provided JSON without validating that the objects in the array conform to the ClusterSummary interface. Subsequent code, such as the filtering logic, accesses required properties like cluster.project_ids without defensive checks. If a user pastes JSON where objects are missing this property, the application will crash with a TypeError when cluster.project_ids.some() is called. This affects a developer-facing tool within the production UI.

💡 Suggested Fix

Implement a type guard or use a validation library (like Zod) to properly validate the structure of each object in the parsed JSON array against the ClusterSummary interface before casting and setting the state with setCustomClusterData. This ensures all required properties exist before they are accessed.

🤖 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/views/issueList/pages/topIssues.tsx#L961-L963

Potential issue: The `handleParseJson` function uses a type assertion `as
ClusterSummary[]` on user-provided JSON without validating that the objects in the array
conform to the `ClusterSummary` interface. Subsequent code, such as the filtering logic,
accesses required properties like `cluster.project_ids` without defensive checks. If a
user pastes JSON where objects are missing this property, the application will crash
with a `TypeError` when `cluster.project_ids.some()` is called. This affects a
developer-facing tool within the production UI.

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

[cursor]

Loading indicator shown when custom data is loaded

When custom JSON data is loaded via the dev tool, the isPending check doesn't account for customClusterData being present. If a user loads custom data before the API query completes (or if the query is slow/fails), isPending may still be true from the original query, causing the LoadingIndicator to display instead of the custom cluster data. The condition needs to also check !isUsingCustomData or !customClusterData.