Change auto-deletion throttling constants to better scale with server size

[ClearlyClaire]

• MAX_BUDGET: increase from 50 per minute to 150 per minute, as 50 per minute might be too low to keep up with mastodon.social's 56~96 new posts per minute (though the number of toots to be auto-deleted is probably far lower)
• PER_THREAD_BUDGET: increase from 5 to 6 per minute, this is more to give more leeway to small servers
• MAX_DEFAULT_SIZE: increase from 2 to 200 items, as larger servers will have larger queues (while still quickly chewing through them), a limit of 2 items is not reasonable, as a server with any medium activity will often have more than that
• MAX_PUSH_SIZE: increase from 5 to 500 items, as larger servers will have larger queues (while still quickly chewing through them), a limit of 5 items is not reasonable, as a server with any medium activity will often have more than that
• MAX_PULL_SIZE: increase from 500 to 10000 items since larger servers will frequently queue very large amounts of low-priority jobs
• MAX_RETRY_SIZE: dropped it as it's widely inconsistent across servers and is not directly indicative of load

Also changed the lock TTL to 1 day, which is plenty enough since the job itself is expected to finish in seconds, and will check for load.

[github-actions]

This pull request has merge conflicts that must be resolved before it can be merged.