Fix sidekiq:migrate_jobs tasks in production mode

The whole file was skipped, when only the YAML-generation tasks should
have been.

Changelog: fixed

lib/tasks/gitlab/sidekiq.rake

 # frozen_string_literal: true
 
-return if Rails.env.production?
-
 namespace :gitlab do
   namespace :sidekiq do
     def write_yaml(path, banner, object)
@@ -31,9 +29,13 @@ namespace :gitlab do
       end
     end
 
+    task :not_production do
+      raise 'This task cannot be run in the production environment' if Rails.env.production?
+    end
+
     namespace :all_queues_yml do
       desc 'GitLab | Sidekiq | Generate all_queues.yml based on worker definitions'
-      task generate: :environment do
+      task generate: ['gitlab:sidekiq:not_production', :environment] do
         banner = <<~BANNER
           # This file is generated automatically by
           #   bin/rake gitlab:sidekiq:all_queues_yml:generate
@@ -51,7 +53,7 @@ namespace :gitlab do
       end
 
       desc 'GitLab | Sidekiq | Validate that all_queues.yml matches worker definitions'
-      task check: :environment do
+      task check: ['gitlab:sidekiq:not_production', :environment] do
         if Gitlab::SidekiqConfig.all_queues_yml_outdated?
           raise <<~MSG
             Changes in worker queues found, please update the metadata by running:
@@ -70,7 +72,7 @@ namespace :gitlab do
 
     namespace :sidekiq_queues_yml do
       desc 'GitLab | Sidekiq | Generate sidekiq_queues.yml based on worker definitions'
-      task generate: :environment do
+      task generate: ['gitlab:sidekiq:not_production', :environment] do
         banner = <<~BANNER
           # This file is generated automatically by
           #   bin/rake gitlab:sidekiq:sidekiq_queues_yml:generate
@@ -104,7 +106,7 @@ namespace :gitlab do
       end
 
       desc 'GitLab | Sidekiq | Validate that sidekiq_queues.yml matches worker definitions'
-      task check: :environment do
+      task check: ['gitlab:sidekiq:not_production', :environment] do
         if Gitlab::SidekiqConfig.sidekiq_queues_yml_outdated?
           raise <<~MSG
             Changes in worker queues found, please update the metadata by running: