Fix failure in spec/services/groups/autocomplete_service_spec.rb

Closes #8777

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

Epic issue list and related issue list re-design

Closes #6086

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

You can't add user to subgroup with lower access level than parent group
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Port to EE: Resolve "Navigating unresolved discussions on Merge Request page"

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

EE Compat Version for Resolve "Extended User Centric Tooltips"

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

Group SAML SSO page warns when linking account

Closes #8260

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

Port "Utilize new charting library for metrics dashboard" to EE

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

Integrate csslab (EE)

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

This commit includes all the changes from the CE
branch: 51122-fix-navigating-discussions to port
the changes to EE.

Linking an account allows the external service to sign that user into
GitLab. We need to make users aware of this to reduce the risk of
phishing attacks where users are maliciously tricked into linking
accounts.

We do this by showing a warning and including the group path and the
URL that the user will be redirected to. We also limit the URL to
ASCII characters to avoid homoglyph attacks.

Replace the metrics dashboard graph with
GitLab UI's area chart component

Add information regarding Elasticsearch and deleted documents

Closes #7611

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

CE upstream - 2018-12-07 02:38 UTC

Closes gitlab-ce#54729, gitlab-ce#52607, #2745, and gitlab-ce#54718

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

Add feature flag for Dependency Scanning reports parsing

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

Add milestones autocomplete for epics

Closes #5603

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

Allow public forks to be deduplicated

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

As discussed in:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/23508#note_123296899

Snapshotting doesn't use git, and will miss the required shared data.

When a project is forked, the new repository used to be a deep copy of everything
stored on disk by leveraging `git clone`. This works well, and makes isolation
between repository easy. However, the clone is at the start 100% the same as the
origin repository. And in the case of the objects in the object directory, this
is almost always going to be a lot of duplication.

Object Pools are a way to create a third repository that essentially only exists
for its 'objects' subdirectory. This third repository's object directory will be
set as alternate location for objects. This means that in the case an object is
missing in the local repository, git will look in another location. This other
location is the object pool repository.

When Git performs garbage collection, it's smart enough to check the
alternate location. When objects are duplicated, it will allow git to
throw one copy away. This copy is on the local repository, where to pool
remains as is.

These pools have an origin location, which for now will always be a
repository that itself is not a fork. When the root of a fork network is
forked by a user, the fork still clones the full repository. Async, the
pool repository will be created.

Either one of these processes can be done earlier than the other. To
handle this race condition, the Join ObjectPool operation is
idempotent. Given its idempotent, we can schedule it twice, with the
same effect.

To accommodate the holding of state two migrations have been added.
1. Added a state column to the pool_repositories column. This column is
managed by the state machine, allowing for hooks on transitions.
2. pool_repositories now has a source_project_id. This column in
convenient to have for multiple reasons: it has a unique index allowing
the database to handle race conditions when creating a new record. Also,
it's nice to know who the host is. As that's a short link to the fork
networks root.

Object pools are only available for public project, which use hashed
storage and when forking from the root of the fork network. (That is,
the project being forked from itself isn't a fork)

In this commit message I use both ObjectPool and Pool repositories,
which are alike, but different from each other. ObjectPool refers to
whatever is on the disk stored and managed by Gitaly. PoolRepository is
the record in the database.

Port "Further improvements to Project overview UI" to EE

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

Web Terminal FE

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

[EE] Remove RemoveOldWebHookLogsWorker

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

Revert "Add instance-level maven endpoint for download"

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

Fix ability to choose shards for selective sync

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

Fix transaction pollution in Shard.by_name (EE)

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

Resolve "Add subscription table to GitLab.com billing areas"

Closes #7772

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

Documentation for "`only/except: merge-requests` for merge request pipelines"

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

This reverts commit d2f55f9a.