Fix OpenID Connect documentation

See merge request gitlab-org/gitlab-ce!29314

Make OpenID Connect work without requiring a name

Closes #62208

See merge request gitlab-org/gitlab-ce!29312

docs - add section to dev docs on accessing chatops

Closes #62127

See merge request gitlab-org/gitlab-ce!28623

closes 62127

Port missing docs to CE

See merge request gitlab-org/gitlab-ce!29279

Add docs for breaking changes of GitLab CI in 12.0

See merge request gitlab-org/gitlab-ce!29053

Visit project after push

Closes gitlab-org/quality/nightly#105

See merge request gitlab-org/gitlab-ce!29247

Removes duplicated shared_context folder on spec/support

See merge request gitlab-org/gitlab-ce!29305

Adds sidekiq worker label for ruby metrics

Closes #60303

See merge request gitlab-org/gitlab-ce!29215

Many users were unable to get logins working with OpenID Connect because
of a missing `name` argument in the configuration. This resulted in 404s
immediately after attempting to login. This describes the workaround
mentioned in
https://gitlab.com/gitlab-org/gitlab-ce/issues/62208#note_178774809.

This also adds an example profile for using Google.

If there is no name argument given, OmniAuth will try to guess the name
by the class name. In
https://github.com/omniauth/omniauth/blob/v1.9.0/lib/omniauth/strategy.rb#L139,
`OmniAuth::Strategies::OpenIDConnect` gets translated to
`openidconnect`.

This leads to an immediate 404 error after clicking the login button
because OmniAuth can't match the current route (/users/auth/openid_connect)
against the expected one (/users/auth/openidconnect).

Other providers, such as Google OAuth2, set this name as the default
option within the OmniAuth Strategy. Until a fix is merged upstream,
let's just set the parameter ourselves.

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

FE display for "Specify that an MR must be merged after another MR"

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

Replace mock response with real data

Closes #11759

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

Change response schema and return not only a list of dependencies
but status and ci job path.
As well, replased mock data with dependency list report data.

Most of the shared context are located under
spec/support/shared_contexts, we only have one file under
spec/support/shared_context, this MR moves it to
spec/support/shared_contexts instead

Port Configure Feature Flags Modal to Vue

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

Add frontend support for cluster health alerts

Closes #5456

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

Adds a new query text input for metric alerts

Backport: Add frontend support for cluster health alerts

See merge request gitlab-org/gitlab-ce!29075

Adds a new query text input for metric alerts

CE backport for Storage Counter changes

Closes #59232

See merge request gitlab-org/gitlab-ce!29206

Adds Storage Counter

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

This commits updates the text in the
empty state to reflect it being used
in the user profile and the group settings

Don't fail the pipeline when a colon-emoji is used

See merge request gitlab-org/gitlab-ce!29291

Add certificate valid time to pages domain table

See merge request gitlab-org/gitlab-ce!29287

Save certificate validity time for pages domains on save
Fill validity time for existing pages domains in background migration

Add pages domains acme orders

See merge request gitlab-org/gitlab-ce!27811

Extract acme double to helper

Create ACME challanges for pages domains

* Create order & challange through API
* save them to database
* request challenge validation

We're saving order and challenge as one entity,
that wouldn't be correct if we would order certificates for
several domains simultaneously, but we always order certificate
per domain

Add controller for processing acme challenges redirected from pages

Don't save acme challenge url - we don't use it

Validate acme challenge attributes

Encrypt private_key in acme orders

EE port of Add pages domains acme orders

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

A colon-emoji like 💯 can be valid in the case where we're talking
about the GitLab feature that processes these into emojis. It's fine to
warn about those, but failing the pipeline is too restrictive.

Extract acme double to helper

Create ACME challanges for pages domains

* Create order & challange through API
* save them to database
* request challenge validation

We're saving order and challenge as one entity,
that wouldn't be correct if we would order certificates for
several domains simultaneously, but we always order certificate
per domain

Add controller for processing acme challenges redirected from pages

Don't save acme challenge url - we don't use it

Validate acme challenge attributes

Encrypt private_key in acme orders