Geo: Run concurrency limit worker on secondary sites

What does this MR do and why?

Geo secondaries can accumulate throttled jobs such as Geo::EventWorker, but the resume logic was not reliably running there because secondary cron management disabled concurrency_limit_resume_worker (it disables all cron jobs by default, besides those necessary for replication/verification).

This MR updates Geo secondary cron behavior so ConcurrencyLimit::ResumeWorker runs on secondary sites, enabling automatic draining of concurrency-limit throttled Geo jobs.

References

• Relates to #595824
• Related background in #591124 (closed)

How to set up and validate locally

• Set up Geo with a primary and a secondary.
• Confirm concurrency_limit_resume_worker remains enabled on the secondary.
• Create load that throttles Geo jobs (Geo::EventWorker / Geo::SyncWorker).
• Verify throttled Redis lists are drained automatically by ConcurrencyLimit::ResumeWorker and Geo replication catches up.