This adds tracking of merged requests when creating deployments. These
changes are hidden behind a feature flag at the moment, and no UI or
APIs have been added yet.

By tracking merge requests, developers will eventually be able to easily
see when their merge requests made it into a certain environment. This
data also allows for more accurate measuring of the time between a merge
request getting merged and deployed to a certain environment.

See https://gitlab.com/gitlab-org/gitlab/issues/32584 for more
information.
Co-authored-by: Alessio Caiazza <acaiazza@gitlab.com>

Add guard to avoid misleading error message

See merge request gitlab-org/gitlab!19487

Update plantuml.md with URI rewrite for nginx

See merge request gitlab-org/gitlab!19163

Revert "Merge branch 'mc/backstage/needs-canonical-form' into 'master'"

See merge request gitlab-org/gitlab!19479

Update praefect git_data_dirs setup

Closes gitaly#2111

See merge request gitlab-org/gitlab!19040

Add API for suggesting unique alternatives if username exists

See merge request gitlab-org/gitlab!19303

This reverts merge request !17539

Replace end-to-end test by rspec test

Closes #33549

See merge request gitlab-org/gitlab!19445

Extend gRPC timeouts for Rake tasks

Closes #22398

See merge request gitlab-org/gitlab!19461

Edited notifications docs

See merge request gitlab-org/gitlab!19341

* Edited and restructured notification docs to improve
clarity.
* Issue: https://gitlab.com/gitlab-org/gitlab/issues/31710

Remove non-api tests from api spec

Closes #32903

See merge request gitlab-org/gitlab!19219

Fix file locking spec and quarantine locks directory spec

See merge request gitlab-org/gitlab!19380

Test was quarantined due to a bug: https://gitlab.com/gitlab-org/gitlab/issues/35254
Changed hardcoded "Adminstrator" in expectation to a username

In https://gitlab.com/gitlab-org/gitlab/merge_requests/16926 we added
gRPC timeouts for calls that did not previously have timeouts to prevent
Sidekiq queries from getting stuck. In addition, we also made long
timeouts 55 seconds for non-Sidekiq requests, but this meant Rake tasks
also fell into this bucket. Rake backup tasks with large repositories
would fail because the CreateBundle RPC would time out after 55 seconds.

To avoid this trap, we flip the logic of long_timeout: instead of
checking for Sidekiq (or other background jobs), we only lower the
timeout to 55 seconds if we're servicing a Web request in Puma or
Unicorn.

Closes https://gitlab.com/gitlab-org/gitlab/issues/22398

Update github_integration.md

See merge request gitlab-org/gitlab!19452

Correct typo in documentation

See merge request gitlab-org/gitlab!19462

Update docs to show how to make report artifact downloadable

See merge request gitlab-org/gitlab!19426

GitLab EKS Cluster backend services

See merge request gitlab-org/gitlab!16758

Add a machine-readable graphql schema

See merge request gitlab-org/gitlab!19199

Add `edit` endpoint for Release page

See merge request gitlab-org/gitlab!17858

There are several steps to this process:

* GitLab assumes the role provided by the user and stores
  a set of temporary credentials on the provider record. By default
  these credentials are valid for one hour.

* A CloudFormation stack is created, based on the template in
  vendor/aws/cloudformation/eks_cluster.yaml. This triggers creation
  of all resources required for an EKS cluster.

* GitLab polls the status of the stack until all resources are ready,
  which takes somewhere between 10 and 15 minutes in most cases.

* When the cluster is ready, GitLab stores the cluster details and
  fetches another set of temporary credentials, this time to allow
  connecting to the cluster via Kubeclient. These credentials
  are valid for one minute.

* GitLab configures the worker nodes so that they are able to
  authenticate to the cluster, and creates a service account for
  itself for future operations.

* Finally, all details and credentials that are no longer required
  are removed.

Updated to kubectl v1.13.12 and helm v2.15.1

See merge request gitlab-org/gitlab!18924

Fix stuck ci jobs worker

Closes #34749

See merge request gitlab-org/gitlab!19465

Add heatmap chart support

See merge request gitlab-org/gitlab!16559

This adds the support to add heatmap charts to the monitoring
dashboard, via the use of the custom dashboards feature

Option to prevent LDAP sign in

Closes #15626

See merge request gitlab-org/gitlab!18749

When LDAP is used for group sync and SAML for authentication,
it can be preferable to disable LDAP sign in for security.

Issues like https://gitlab.com/gitlab-org/gitlab/issues/34749 show, that
the worker is vulnerable for exceptions happening during model update in
DB. What's worse is that exceptios happening on this level, are failing
the whole execution of StuckCiJobsWorker, which unnoticed ends with
thousands of stale pending/running/scheduled jobs waiting in the queue.

This commit re-uses the fix added with
https://gitlab.com/gitlab-org/gitlab/merge_requests/19150 to properly
handle and log such exceptions and drop the jobs regardless of them.

Geo - Rename Geo::FileRegistry model to Geo::UploadRegistry

Closes #10067

See merge request gitlab-org/gitlab!19251

The file_registry table only tracks uploads. This commit
renames the model to make the model's intent more clear.

This commit also removes some uncessary joins.

Gitlab::Tracking data point for VisualReviewDiscussion API

Closes #11944

See merge request gitlab-org/gitlab!18890

Merge branch '10286-geo-sql-statement-times-out-whilst-determining-lfs-objects-to-sync' into 'master'

Geo - Rewrite query to determine LFS objects to sync with selective sync

Closes #10286

See merge request gitlab-org/gitlab!19051

Count how many zoom calls are linked to issues

See merge request gitlab-org/gitlab!18967

Add real world config to overcommit example

See merge request gitlab-org/gitlab!19322