Add a circuit breaker to prevent data migration jobs from saturating Sidekiq

Background

We had customer reports where retrying failed data migration jobs saturated their Sidekiq, for example #413113 (closed). We should have some mechanism to prevent this from happening.

Proposal

The team has discussed and proposed adding a circuit breaker in the logic where we decide to re-queue or not re-queue the failed data migration jobs.