Check if shard configuration is same across Geo nodes

Closes #3243

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

Update Kubernetes service documentation

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

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

States this service was deprecated on 10.3 and his behavior depends on
the kubernetes service status. Also includes a link for the release post
for more information.

CE Port: 41054 Disable creation of new kubernetes integrations

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

EE: Unify CE and EE tests in spec/controllers/projects/artifacts_controller_spec.rb

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

EE: Enable our own custom cops, again?

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

Show correct edition for EE free

Closes gitlab-ce#41092

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

Fix namespace ambiguity with Kubernetes Pod definitions

Closes #4468

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

This was causing a spec failure between Gitlab::Kubernetes::Helm::Pod and
Gitlab::Kubernetes::Helm::Api::Pod if one spec loaded the former
definition first.

Closes #41458

Fix a bug where branch could not be delete due to a push rule config

Closes #4078

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

Move git operations for UpdateRemoteMirrorService into Gitlab::Git

Closes gitaly#841

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

Prepare Gitlab::Git::Repository#rebase for Gitaly migration

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

Geo backend changes for Vue admin page

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

Improve closed/merged events queries performance on Projects::MergeRequestsController#show.json

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

More descriptive error when clocks between Geo nodes are out of sync

Closes #4276

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

This merge request will allow the primary to compare its storage configuration
against the secondaries. Not that the status only works if you view the admin
page on the primary, since the secondaries don't have access to the primary.

How it works:

1. The primary will populate the GeoNode index page with a JSON of the current configuration
2. The primary will download the latest configuration with the `/api/v4/geo/status` endpoint
3. The JavaScript on the frontend will do a simple equality comparison between the arrays

Since the shard configuration is currently stored in `gitlab.yml`, I've
purposely tried avoided storing the shard configuration in the database to
avoid multiple sources of the truth.

Closes #3243

Add step to run gitlab:geo:check on primary

Closes #4088

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

Port of da-handle-hashed-storage-repos-using-repo-import-task to EE

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

In case there is a large difference between the system clocks of
different Geo nodes (> 60 seconds) the JWToken won't be valid. Make
this error more descriptive so sysadmins can identify the problem.

Closes gitlab-org/gitlab-ee#4276