Move GitLab Migration sidekiq jobs to the dedicated imports shard
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=342441) </details> <!--IssueSummary end--> Currently, GitLab Migration (Bulk Import) sidekiq jobs run on the `default` shard. We should consider moving the sidekiq jobs for GitLab Migration processes to the dedicated `imports` shard ([similar to `RepositoryImportWorker`](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/blob/bab51c1c248778789a5a1f87358aaeba412d61c6/releases/gitlab/values/gprd.yaml.gotmpl#L449)) in order to minimize disruptions to long-running (large) imports.
issue