chore(seer): optimize scanner rate limiting

[roaga]

• Bump scanner rate limit to 2500 per hour. Since we now scan existing issues as well, and since we double-count in slack alerts, we're going to be hitting the rate limit a lot more. This is still respectable for budgets, capping at $7.50.
• Only increment and check rate limit after we pass the quota check and are about to start a scanner task. Right now we're logging rate limit exceeded errors for customers without any quota.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

⚠️ Parser warning

The parser emitted a warning. Please review your JUnit XML file:

Warning while parsing testcase attributes: Limit of string is 1000 chars, for name, we got 2083 at 1:160664 in /home/runner/work/sentry/sentry/.artifacts/pytest.junit.xml

Additional details and impacted files

@@           Coverage Diff           @@
##           master   #93928   +/-   ##
=======================================
  Coverage   88.03%   88.03%           
=======================================
  Files       10342    10342           
  Lines      597312   597362   +50     
  Branches    23212    23212           
=======================================
+ Hits       525842   525890   +48     
- Misses      70965    70967    +2     
  Partials      505      505           

[JoshFerge]

worth adding a test?

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ OperationalError: connection to server at "127.0.0... in prod

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