Rate limit user report ingestion

[aliu39]

Problem Statement

Relates to
https://github.com/getsentry/team-replay/issues/436
https://github.com/getsentry/sentry-options-automator/pull/1422
https://github.com/getsentry/getsentry/pull/14582

There are still a few orgs on the denylist for old and new feedback. We'd prefer not to block them manually like this, as its hard to maintain and based on past situations. But removing them all at once could cause problematic load on our processing pipeline (spam + issues platform).

Solution Brainstorm

We can rate limit in relay (for user_report(v1) items) and sentry entrypoints (save_userreport). We need to decide on and test different limits. It's also important to ensure fairness between the different types of feedback -- there should be separate quotas for crash reports and widget.

Product Area

User Feedback

[getsantry]

Routing to @getsentry/product-owners-user-feedback for triage ⏲️

[aliu39]

This issue can be split in 2. 1) Rate limiting ingest due to load concerns, and 2) quotas for the overall feature. Feedback is a free feature so we can table 2 for now (what I was talking about above in "there should be separate quotas..").

To remove the deny-lists, we just need reasonable rate limits for user reports in relay, and the crash report endpoint in Sentry.

[aliu39]

relates to https://github.com/getsentry/getsentry/pull/12177/files and https://github.com/getsentry/team-replay/issues/287