[Replay] Ensure we avoid sending replays when hitting rate limits

[mydea]

We need to make sure we do not try to send any replays when hitting rate limits. If we hit a rate limit, we should wait until sending any further replay data until the rate limit expires.

Open questions:

• Should we "just" discard any stuff that should be sent while the rate limit applies?
• Or should we keep the recording data and try to send it all later, when the rate limit is over?

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[Lms24]

We should already handle this as transports internally respect rate-limits:

sentry-javascript/packages/core/src/transports/base.ts

Lines 51 to 60 in c8c972b

	forEachEnvelopeItem(envelope, (item, type) => {
	const envelopeItemDataCategory = envelopeItemTypeToDataCategory(type);
	if (isRateLimited(rateLimits, envelopeItemDataCategory)) {
	const event: Event | undefined = getEventForEnvelopeItem(item, type);
	options.recordDroppedEvent('ratelimit_backoff', envelopeItemDataCategory, event);
	} else {
	filteredEnvelopeItems.push(item);
	}
	});

[Lms24]

Gonna close this issue as we have a more general rate-limiting issue now: #6710