Draft: Limit concurrency of repository cleanup jobs [skip ci]
What does this MR do and why?
Repository cleanup jobs write to the database in proportion to the amount of rewritten history, and any number of them can run at the same time.
This MR limits how many repository cleanup jobs run concurrently, and defers them while the database reports an unhealthy state, so they back off instead of adding to the load.
It was split out of !265959 (merged), which bounds the database transactions of repository cleanup. That change can ship without this one, while the right concurrency limit and deferral settings are still being evaluated.
Related to https://gitlab.com/gitlab-org/gitlab/-/work_items/634218
References
Screenshots or screen recordings
Not applicable, there is no UI change.
How to set up and validate locally
Not applicable, this changes Sidekiq worker scheduling only.
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.