chore(jest): update known flaky tests

[cursor]

Updates it.isKnownFlake markers based on current flakiness data from the jest project on Sentry (spanning the past 7 days on refs/heads/master).

Newly marked as isKnownFlake (≥2 failures in 7 days):

• metricsTab.spec.tsx: "should add a metric when Add Metric button is clicked" (6 failures), "should switch to aggregate mode when a group by is added" (2 failures)
• apiTokenDetails.spec.tsx: "does not accept long name" (5 failures)
• commandPaletteGlobalActions.spec.tsx: 3 tests with 3 failures each
• whatsNew.spec.tsx: "renders empty state when API returns no broadcasts" (3 failures)
• logs.spec.tsx (react-native): "shows React Native logs onboarding content" (3 failures)
• onboarding.spec.tsx (java-log4j2): "renders maven docs correctly" (2 failures)
• archive.spec.tsx: "archives forever" (2 failures)
• searchBar.spec.tsx (issueList): "displays the correct options for the is tag" (2 failures)
• stacktraceLink.spec.tsx: "renders setup CTA with integration but no configs" (2 failures)
• autofixOutputStream.spec.tsx: "renders basic stream content" (2 failures)
• boostrapRequests.spec.tsx: "updates team store with fetched data" (2 failures)

Un-marked (no longer appearing in flaky list):

• eventReplay/index.spec.tsx: "should render the replay inline onboarding component..."
• spanEvidencePreview.spec.tsx: "shows error when request fails"
• allMonitors.spec.tsx: "shows option to select all query results..."
• resultsSearchQueryBuilder.spec.tsx: "shows normal tags, e.g. transaction, in the dropdown"
• metricsTab.spec.tsx: "disables both Add Metric and Add Equation buttons..."
• useReplaysFromIssue.spec.tsx: "should fetch a list of replay ids"
• trace.spec.tsx: "does not render the summary tab..."

Dashboard: https://sentry.sentry.io/dashboard/4627175/?environment=ci%3Amaster&project=4857230&statsPeriod=7d

  

[ryan953]

@cursoragent iterate on this until CI checks are passing

[cursor]

The CI failure shown (getsentry dispatch) is unrelated to the code changes and is expected for bot-created PRs.

Current Status

✅ All required CI checks are passing:

• pre-commit lint ✅ (was failing due to formatting, now fixed)
• Acceptance ✅
• Backend ✅
• Frontend ✅

❌ getsentry dispatch - This is failing due to permissions, not code issues. The error message states:

permissions failed!
- has write permission: False
- has [Trigger: getsentry tests] label: False

This check requires either:

1. Write permissions to the repository (which bots don't have), OR
2. A collaborator to add the [Trigger: getsentry tests] label after reviewing the code

What I Fixed

The actual code issue (formatting of it.isKnownFlake markers) has been resolved. The formatter needed the test declarations wrapped across multiple lines for readability.

Conclusion

The PR is ready for review. The getsentry dispatch failure is an expected infrastructure limitation for bot PRs and doesn't indicate any problem with the code changes. A human collaborator with write access can add the label if those additional tests are needed.