Remove the token sweep from the IAM reconciliation cron
What does this MR do and why?
Do not merge yet. Merge it when the bulk jobs are tested on staging (https://gitlab.com/gitlab-org/gitlab/-/work_items/634258).
Removes the authn_iam_replication_reconciliation_oauth_access_tokens cron entry. The worker and the refresh token replicator do not change. The OAuth application sweep keeps its entry.
Both Layer 4 sweeps run when iam_data_replication is enabled. For the backfill into an empty IAM, the application sweep must finish one full pass before the token sweep starts. The staging run shows why (https://gitlab.com/gitlab-org/gitlab/-/work_items/632070#note_4119283817): IAM refuses a token until its application is in IAM, and the two sweeps share the concurrency limit of the worker. A later MR adds the entry back.
On deploy, sidekiq-cron removes the job, because the schedule loads with source: 'schedule' (https://gitlab.com/gitlab-org/gitlab/-/blob/master/lib/gitlab/sidekiq_config/cron_job_initializer.rb#L31).
References
- Step 3 of https://gitlab.com/gitlab-org/gitlab/-/work_items/634258 (staging). https://gitlab.com/gitlab-org/gitlab/-/work_items/634260 runs the same steps on production.
How to set up and validate locally
bin/rspec ee/spec/initializers/1_settings_spec.rb