Long-term rate limits for package uploads.

[isoos]

• Create an allow-list of packages that can publish more than 1000 versions #8053
• The current rate limit implementation relies on reading all of the audit log records from the datastore and keeping them in memory. While we could read a full year's worth of logs into the memory, it seemed better to provide a separate path for package uploads, as we do have the timestamps at the time of rate limit checks.
• I've added additional checks that (a) we shouldn't specify long-term rate limits for other actions and (b) if we do and we don't provide the timestamps, it should fail.
• In order to reduce the surprises, I think we could start introducing the weekly limit, and then shortly after that the monthly, while the quarterly limit should be added only later this year, and the yearly in the next year. That way packages that would be over the specific limit have time to adopt.
• Giving a feedback of the remaining limit may come in a subsequent PR.