Add missing dictionary file for batched migration

What does this MR do and why?

This MR fixes the problem described in gitlab-org/quality/engineering-productivity/master-broken-incidents#9934 (comment 2301606795) by adding a missing dictionary file for batched migration, together with a derived job.

Create new derived RequeueDeleteOrphanedPartitionedCiRunnerMachineRecords job and preserve previous dictionary file for DeleteOrphanedPartitionedCiRunnerMachineRecords.

Context

• I first created 20241231094025_requeue_delete_orphaned_p_ci_runner_machine_records_on_dot_com.rb in %17.6.
• This file was no-oped and requeued with 20241231094025_requeue_delete_orphaned_p_ci_runner_machine_records_on_dot_com.rb in %17.8 (a required stop), following the instructions in the documentation.
• I made a mistake was when I needed to run the same migration for all deployments (not just .com), I created 20250113164152_requeue_delete_orphaned_partitioned_ci_runner_machine_records.rb reusing the same BatchedMigrationJob-derived class, and therefore using the same dictionary file. This MR fixes it by creating the derived job, corresponding dictionary file, and resetting the contents of the original job dictionary file.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

• Friday 2025-01-17 00:02 UTC - `gitlab-org/gitla... (gitlab-org/quality/engineering-productivity/master-broken-incidents#9934 - closed)
• Delete orphaned records on ci_runner_machines_6... (#504297 - closed)
• Remove orphaned managers from .com ci_runner_ma... (!176702 - merged)

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.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

n/a

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Run bundle exec rubocop db/post_migrate/20241231094025_requeue_delete_orphaned_p_ci_runner_machine_records_on_dot_com.rb db/post_migrate/20250113164152_requeue_delete_orphaned_partitioned_ci_runner_machine_records.rb.