Put Geo::MetricsUpdateWorker behind a feature flag
What does this MR do and why?
Puts Geo::MetricsUpdateWorker
behind a feature flag. We've been seeing Geo::MetricsUpdateWorker performance issues with very large tables. So we should probably assume that some issue like that will pop up on GitLab.com due to its scale. With it behind a feature flag, we can stop this worker from running if its queries cause excessive load without blocking all other Geo activities, e.g., checksumming.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related issues
Related to #499371 (closed)
Edited by Douglas Barbosa Alexandre