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

- it would be nice to have a working file in here as an
  example file.
- this brings us one step closer to hopefully utilizing
  overcommit in CI and/or at least on each dev's machine
- next step would be for gdk install to copy it over,
  drop the extension and install it
- or drop the .example on this file and make it the default,
  and users will merely have to run a `overcommit -i` after
  installing overcommit gem

Merge branch '10067-fix-migration-to-insert-lfs-objects-entries-into-their-own-registry-table' into 'master'

Geo - Fix migration to migrate LFS objects entries into their own registry table

Closes #10067

See merge request gitlab-org/gitlab!19395

Add support for basic parallelization of the 'static-analysis' job

Closes #34318

See merge request gitlab-org/gitlab!19379

Revert "Sort wiki pages by date"

See merge request gitlab-org/gitlab!19403

Add ApplicationSetting snowplow_iglu_registry_url

See merge request gitlab-org/gitlab!18449

Adds snowplow_iglu_registry_url to ApplicationSettings.

The Iglu Schema Registry is used for Contextual Snowplow events.

Fix last_deployment Eager Load for Environment Dashboard

See merge request gitlab-org/gitlab!18935

This commit optimizes envrionment dashboard query

Fix cluster feature highlight popover image

See merge request gitlab-org/gitlab!19372

Fixed the popover image by disabling lazy-loading