Don't emit Sentry warnings for throttled queries to Snuba

[xurui-c]

Allocation policies are our mechanism for doing traffic management for Snuba queries. Currently, we see a lot of warnings (Warning: Query from referrer ... is throttled) on Sentry Issues. This is because these queries are throttled due to being in the "warning zone"; however, we got feedback that this isn't actually actionable, so we're getting rid of them. We will only emit Sentry errors for rejected queries.

[sentry[bot]]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: src/sentry/utils/snuba.py

Function	Unhandled Issue
_apply_cache_and_build_results	RateLimitExceeded: Query on could not be run due to allocation policies, info: {'details': {'ConcurrentRateLimitAllo... ... Event Count: 404
_apply_cache_and_build_results	SnubaError: Unexpected EOF while reading bytes se... Event Count: 28
_apply_cache_and_build_results	SnubaError: Unexpected EOF while reading bytes se... Event Count: 10
_apply_cache_and_build_results	SnubaError: Unexpected EOF while reading bytes se... Event Count: 7
_apply_cache_and_build_results	UnqualifiedQueryError: validation failed for entity events: missing required conditions for project_id ... Event Count: 2

---

_{Did you find this useful? React with a 👍 or 👎}