Remove migration worker files and update queues yml

What does this MR do and why?

In this MR, we remove the worker files and add a migration with sidekiq_remove_jobs for the removed workers. This is the next step after the workers have been updated to no-operation in !147228 (merged) in %16.11.

Issue for removing the migration workers (#409873 (closed))

From the guideline:

1. Delete the worker class file and follow the guidance in our Sidekiq queues documentation around running Rake tasks to regenerate/update related files.
2. Add a migration (not a post-deployment migration) that uses sidekiq_remove_jobs

The queues YAML files were updated by running:

• bin/rake gitlab:sidekiq:all_queues_yml:generate
• bin/rake gitlab:sidekiq:sidekiq_queues_yml:generate

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.

Migration Result:

main: == [advisory_lock_connection] object_id: 6396580, pg_backend_pid: 58042
ci: == [advisory_lock_connection] object_id: 6398460, pg_backend_pid: 58044
ci: == 20240421143211 RemoveContainerRegistryMigrationWorkers: migrating ==========
ci: -- transaction_open?(nil)
ci:    -> 0.0000s
ci: == 20240421143211 RemoveContainerRegistryMigrationWorkers: migrated (0.0078s) =

Related to #450625 (closed)