This reverts merge request !73512

bin/background_jobs would write to stdout with `start_foreground`, and
to log/sidekiq.log with `start` or `restart`. That was confusing, as
other application log files are in log/ in development. To simplify
this, use `tee` to make `start_foreground` both write to stdout and
log/sidekiq.log.

If you set the SIDEKIQ_QUEUES environment variable, bin/background_jobs
will use that queue list rather than the default ('*'; all queues).

Sets the default number of workers to 1 if SIDEKIQ_WORKERS is not
provided.

This also fixes a bug where we are starting 1 more process than
requested.

It's dangerous when `cd` fails but following commands keeps running
which would lead to expected results.

For those shell scripts without `set -e`, use `exit 1` before furthur
refactor could be a safe and efficient workaround, for thoes shell
scripts with `-e`, the shell(script) will exit immediately if any
command has a non-zero exit status, so they don't need `exit 1`

Reference:
- https://github.com/koalaman/shellcheck/wiki/SC2164

Not all systems having bash in `/bin`.
Use ´/usr/bin/env` to search for bash in `PATH`.

The bin/background_jobs_sk_cluster script use some
bashisms. In order to avoid issues with either GDK
or other systems, here we make use of bash as the
default interpreter.

It simplifies the interface of `bin/background_jobs` as:

1. start - Starting sidekiq or sidekiq-cluster on background.
2. restart - Kill all existing processes and start them
again (in background).
3. start_foreground - Starts sidekiq or sidekiq-cluster on foreground.
4. stop - Well, stops the process.

Here we also split the script into two `bin/background_jobs_sk` and
`bin/background_jobs_sk_cluster`. If `SIDEKIQ_WORKERS` env var is
given we use the `bin/background_jobs_sk_cluster`, which has
basically the same API of the sidekiq counterpart.

Dumping too many jobs in the same queue (e.g. the "default" queue) is a
dangerous setup. Jobs that take a long time to process can effectively
block any other work from being performed given there are enough of
these jobs.

Furthermore it becomes harder to monitor the jobs as a single queue
could contain jobs for different workers. In such a setup the only
reliable way of getting counts per job is to iterate over all jobs in a
queue, which is a rather time consuming process.

By using separate queues for various workers we have better control over
throughput, we can add weight to queues, and we can monitor queues
better. Some workers still use the same queue whenever their work is
related. For example, the various CI pipeline workers use the same
"pipeline" queue.

This commit includes a Rails migration that moves Sidekiq jobs from the
old queues to the new ones. This migration also takes care of doing the
inverse if ever needed. This does require downtime as otherwise new jobs
could be scheduled in the old queues after this migration completes.

This commit also includes an RSpec test that blacklists the use of the
"default" queue and ensures cron workers use the "cronjob" queue.

Fixes gitlab-org/gitlab-ce#23370

Dumping too many jobs in the same queue (e.g. the "default" queue) is a
dangerous setup. Jobs that take a long time to process can effectively
block any other work from being performed given there are enough of
these jobs.

Furthermore it becomes harder to monitor the jobs as a single queue
could contain jobs for different workers. In such a setup the only
reliable way of getting counts per job is to iterate over all jobs in a
queue, which is a rather time consuming process.

By using separate queues for various workers we have better control over
throughput, we can add weight to queues, and we can monitor queues
better. Some workers still use the same queue whenever their work is
related. For example, the various CI pipeline workers use the same
"pipeline" queue.

This commit includes a Rails migration that moves Sidekiq jobs from the
old queues to the new ones. This migration also takes care of doing the
inverse if ever needed. This does require downtime as otherwise new jobs
could be scheduled in the old queues after this migration completes.

This commit also includes an RSpec test that blacklists the use of the
"default" queue and ensures cron workers use the "cronjob" queue.

Fixes gitlab-org/gitlab-ce#23370

When running Unicorn or Sidekiq in the foreground this change removes
an intermediate /bin/sh process. This makes process supervision in the
GitLab Development Kit more reliable.

This change does not affect Omnibus-GitLab (because there we do not
use these launch scripts). Installations from source do use the launch
scripts but for the standard GitLab init script this change will not
make a difference.

Custom installations using Upstart or Systemd may be affected however,
because under certain configurations these systems count exactly how
many forks happen during process startup, and we are reducing that
number by one here.

This behavior got lost in the previous commit.

Delete mailer queue because we don't use sidekiq_mailer gem and now the mailer queue doesn't exist any more.

Avoid the background_jobs script killing every process with 'sidekiq' in
its argument string (e.g. 'rake gitlab:sidekiq start') by also catching
the number (2) in 'sidekiq 2.14'.

This syntax is compatible with the current Sidekiq version we use
(2.17.0) and it protects us against future breakage by
https://github.com/mperham/sidekiq/commit/040eda558bc64139c846c781d3de0b79603e3035

Updated script/{web,background_job} to use #!/usr/bin/env bash rather than #!/bin/bash to allow for transparency between OS namely Linux and FreeBSD and for source installs of bash where path is not exported by default for /usr/local/{bin,sbin}