Geo: Sidekiq cron workers can be re-enabled after a Sidekiq restart
When Sidekiq starts up, we call Gitlab::Geo.configure_cron_jobs!
to enable all relevant Geo Sidekiq jobs. However, on GitLab.com, we periodically restart Sidekiq due to RSS issues, which then causes these jobs to be re-enabled.
This makes it hard to reliably turn off these workers, both for migration purposes and for ruling out database load issues.
One way to solve this is use feature flags to disable the things we want to turn off.
Another way would be to have some sort of flag that disables the automatic configuration of Geo Sidekiq jobs.