Also, enable debug mode.

Signed-off-by: Rémy Coutable <remy@rymai.me>

1. Renames review to review-deploy.
2. Renames stop_review to review-stop.
3. Adds a build-qa-image job to the prepare stage and save the QA
  Docker image as artifact (example:
  https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/120967019).
4. Adds a manual review-qa job to the test stage to run QA tests
  against the Review App (example:
  https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/120967238).
5. Make the review-deploy job plays the review-qa job as soon as the
  Review App is deployed (example:
  https://gitlab.com/gitlab-org/gitlab-ce/-/jobs/120988775

).
6. Updates the Review Apps documentation accordingly.

Signed-off-by: Rémy Coutable <remy@rymai.me>

Ordinarily it would get the `gitlab-org` tag from
`dedicated-no-docs-pull-cache-job`, but adding the `docker` tag
overwrites rather than inherits, so this job has been running on the
underpowered hardware of the shared runners rather than our dedicated
runners.

We're also adding a `high-cpu` tag, which doesn't currently do anything
but will be useful for targeting a runner specifically for this job.

* Defaults to FALSE
* Can be used to disable building/pushing the assets image in the
gitlab:compile:assets job

Signed-off-by: Rémy Coutable <remy@rymai.me>

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54059

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54059

CI jobs will be triggered both with rails 4 and 5
to make sure we keep backward compatibility if it turns out
we have to switch back to rails 4.

Rails 4 jobs are not allowed to fail for now, these jobs will be
removed in a follow-up MR next cycle.

* Don't need to specify stage as it is inherited from the job template

* The job depends on asset image created as part of the
gitlab:assets:compile job.

https://gitlab.com/charts/gitlab/issues/897

Attempt to update google-protobuf for migration-paths

Because the one we were using aren't compatible with
Ruby 2.5.3, and it'll be troublesome to switch Ruby.
Upgrading google-protobuf will be much easier.

All of them will need to be updated for Ruby 2.5.3

We remove oj because we don't really need it and it
doesn't compile on 2.5.3 with that version.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/41825

In `deploy`, if the previous deployment failed, we delete/cleanup all
the objects related to the release, including secrets. The problem is
that if we create the root password before that, it will be then
recreated during the deploy with a random value!

By creatigng the secret just before actually deplying a new release, we
ensure that it won't be overriden.

Signed-off-by: Rémy Coutable <remy@rymai.me>

* Run as part of gitlab:assets:compile job

* Will be used by omnibus-gitlab and the CNG images to avoid
compiling multiple times

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22235

They're no longer used and have no effect

Signed-off-by: Rémy Coutable <remy@rymai.me>

* Use 2 space indentation in review-apps.sh script
* Move automated_review_cleanup back to build stage

* Uses the same supporting code as used in EE
* Includes automated cleanup
* Install external-dns helm chart to review apps cluster if it isn't
already
* Adds variables REVIEW_APPS_AWS_SECRET_KEY and
REVIEW_APPS_AWS_ACCESS_key
* review-apps-ce uses a different cipher

Improve review apps

Closes #6875

See merge request gitlab-org/gitlab-ee!6665

[ci skip]

Signed-off-by: Rémy Coutable <remy@rymai.me>

We disabled a lot of eslint rules on a per-file basis. This checks
touched files for those and reminds you to re-enable the rules and fix
them.

This adds a Dangerfile which executes `prettier` to find out if someone
touched Frontend files and forgot to run it on their current branch.

Refactor scripts/trigger-build and post a commit note with the downstream pipeline URL for omnibus triggers

Signed-off-by: Rémy Coutable <remy@rymai.me>

This is because the CNG pipeline now relies on the assets
compiled here in the gitlab:assets:compile job (It waits
up to 30 minutes for them)

Without this change, the cloud native job was holding up
the pipeline, preventing the assets compile job from being
run.