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

Allow sidekiq to react to becoming a Geo primary or secondary without a restart

Closes #4048

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

Switch some bundles to use Axios --  EE merge edition

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

Resolve "Icons for approvals remaining and approvals met"

Closes #4133

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

EE Port of Multif File Editor File Icons

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

EE: QA: Add a scenario for adding a deploy key

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

Conflicts:
	app/assets/javascripts/boards/boards_bundle.js
	app/assets/javascripts/boards/services/board_service.js
	spec/javascripts/boards/mock_data.js

Before:
/-/boards/1/issues.json?page=1&per=50&scope=all&utf8=✓&state=opened&milestone_title=#upcoming

After:
 /-/boards/1/issues.json?page=1&per=50&scope=all&utf8=%E2%9C%93&state=opened&milestone_title=%23upcoming

Merge remote-tracking branch 'origin/master' into 4133-icons-for-approvals-remaining-and-approvals-met

Update LICENSE to clean up formatting

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

Include the Namespace Id in purchase link for GL.com plans

Closes gitlab-com/customers-gitlab-com#227

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

Resolve "Add wiki total/synced/failed to prometheus metrics"

Closes #4414

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

CE upstream - Saturday

Closes gitlab-ce#36970 and gitlab-qa#122

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

Adjust content width for User Settings, Pipeline quota

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

[ci skip]

[ci skip]

* qa-add-deploy-key:
  Use heredoc so it's more clear
  Put all menus under menu module
  Introduce common project settings and just put
  Introduce Factory::Resource::DeployKey
  Introduce expand_deploy_keys
  Introduce Menu::Side
  Just add a new class to locate the expand button
  Update descriptions and names based on feedback
  Rename DeployKey to DeployKeys
  QA: Add a scenario for adding a deploy key

Port of 40780-choose-file to EE

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

This will automatically select the respective User or Group in the
purchase form used in the subscription portal.