Replays: Self-Serve Bulk Delete System

[zaibkhan]

This PR introduces a self-serve bulk delete system for Replays, enabling large-scale data cleanup and management.

Key changes:

• Adds endpoints and logic for bulk deleting Replay data
• Implements safeguards for performance and safety
• Introduces monitoring hooks for deletion progress
• Improves error handling and rollback for failed deletions

Benchmark reference:
Replicated from ai-code-review-evaluation/sentry-greptile PR #5

[codoki-pr-intelligence]

Codoki PR Review

Summary: Refactor layout components, standardize templates
What’s good: Consistent migration to shared Flex component and removal of duplicate PR comment templates improves maintainability and consistency across integrations.
Review Status: ❌ Requires changes
Overall Priority: Critical
Review Update:
• Scope: Large PR detected (106 files)
• Coverage: Reviewed 30 highest-risk files across 3 batches
• Note: For full confidence, consider splitting this PR; current review covers top 30/106 files

This review covered the top 30 of 106 files (risk-ranked). For complete coverage and faster feedback, consider splitting into ~8 smaller PR(s).

Issues (Critical & High only)

Severity	Issue	Why it matters
Critical	Correctness — Crash when query disabled due to undefined data	…/list/useFeedbackSummary.tsx When the query is disabled (feature flag not present), data is undefined and the code below accesses data.summary and data.numFeedbacksUsed, causing a runtime crash. Guard the disabled/undefined case here so the hook returns safe defaults.
High	Correctness — Mismatched error_id to event data due to zip over dict va...	…/endpoints/project_replay_summarize_breadcrumbs.py Using zip(error_ids, events.values()) assumes nodestore.get_multi preserves insertion order matching error_ids, which is not guaranteed and can mispair IDs with the wrong event data. If one event is missing, zip truncates and further shifts mappings. This can yield incorrect error titles/messages being interleaved for a different error_id.

Showing top 2 issues. Critical: 1, High: 1. See inline suggestions for more.

Key Feedback (click to expand)

• Needs improvement: None identified that would materially impact correctness, security, or performance based on the shown diffs.
• Open questions: Are there downstream references to the removed ParameterizationRegexExperiment or the old PR single-issue template constant in other modules? If so, ensure they are updated to avoid import/runtime errors.

Confidence: 2/5 — Not ready to merge (1 critical · 1 high · status: Requires changes · scope: top 30/106 files reviewed)

React with 👍 or 👎 if you found this review useful.

[codoki-pr-intelligence]

⚠️ High: Using zip(error_ids, events.values()) assumes nodestore.get_multi preserves insertion order matching error_ids, which is not guaranteed and can mispair IDs with the wrong event data. If one event is missing, zip truncates and further shifts mappings. This can yield incorrect error titles/messages being interleaved for a different error_id.

[codoki-pr-intelligence]

🛑 Critical: When the query is disabled (feature flag not present), data is undefined and the code below accesses data.summary and data.numFeedbacksUsed, causing a runtime crash. Guard the disabled/undefined case here so the hook returns safe defaults.

Suggested change

	if (isError) {
	if (isError || !data) {