Revert !149690 into 'master'"

Purpose of revert

To revert !149690 (merged)

Incident: gitlab-com/gl-infra/production#17849 (closed)

Issue with problem description: #456806

Tests are failing in the master pipeline, example of a failing job that has artifacts: https://gitlab.com/gitlab-org/gitlab/-/jobs/6648509052 In those artifacts, in the sidekiq log for example, there are multiple errors showing such as:

/opt/gitlab/embedded/service/gitlab-rails/sidekiq_cluster/cli.rb:62:in `run': invalid option: -m (OptionParser::InvalidOption) from /opt/gitlab/embedded/service/gitlab-rails/bin/sidekiq-cluster:11:in `<main>' /opt/gitlab/embedded/service/gitlab-rails/sidekiq_cluster/cli.rb:62:in `run': invalid option: m (OptionParser::InvalidOption) from /opt/gitlab/embedded/service/gitlab-rails/bin/sidekiq-cluster:11:in `<main>' /opt/gitlab/embedded/service/gitlab-rails/sidekiq_cluster/cli.rb:62:in `run': invalid option: -m (OptionParser::InvalidOption) from /opt/gitlab/embedded/service/gitlab-rails/bin/sidekiq-cluster:11:in `<main>' ...

There are multiple other tests failing / timing out across many jobs, which can be seen in this pipeline here as one example: https://gitlab.com/gitlab-org/gitlab/-/pipelines/1256994352

Checklist

• Create an issue to reinstate the merge request and assign it to the author of the reverted merge request.
• If the revert is to resolve a broken 'master' incident, please read through the Responsibilities of the Broken master resolution DRI.
• If the revert involves a database migration, please read through Deleting existing migrations.
• Add the appropriate labels before the MR is created. We can skip CI/CD jobs only if the labels are added before the CI/CD pipeline is created.

Milestone info

• I am reverting something in the current milestone. No changelog is needed, and I've added a ~"regression:*" label.
• I am reverting something in a different milestone. A changelog is needed, and I've removed the ~"regression:*" label.

Related issues and merge requests