Revert "Merge branch '64341-data-and-privacy-agreement-for-gitlab-users' into 'master'"

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

This reverts merge request !30808

Track views of cycle analytics show page

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

This change adds a new counter 'cycle_analytics_views' to the usage data
metrics to count the page views for cycle analytics show page.

Fix the style-lint errors and warnings for wiki.scss

Closes #59829

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

There were two errors: duplicate styles and @extend used with a class
name. I added `.top-area` class to all the instances where
`.wiki-page-header` is used since %top-area didn't really make a lot of
sense as a placeholder selector. This is also consistent with behaviour
on other pages where the `.top-area` class is used alongside the other
classes for the specific header styling.

Add `ci_dag_limit_needs`

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

Docs add guest user clarification

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

Reduce Gitaly calls in PostReceive

Closes #65878

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

Elasticsearch versioned schema for Snippet

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

This makes to limit `needs:` to 5 by default.
Allow to increase the limit to 50 with disable of FF.

Optimise dag processing

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

Reduce the CE/EE diff under `qa/`

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

Add notification for updated privacy policy

Closes #64341

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

This adds a notification to let users know of our updated privacy
policy.

Users can dismiss the notification either by following the link or
closing the notification via an "x" icon.

Add troubleshooting docs for Registry image push problems

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

CE backport for gitlab-org/gitlab-ee!14894: Fix the merge button dropdown

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

Require `needs:` to be present

Closes #65839

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

Signed-off-by: NRémy Coutable <remy@rymai.me>

Adjust copy for adding additional members

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

Fix spelling of "timeouted" to "timed out"

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

Documentation: fix push options capabilities

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

https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/31068 forgot to
add a short description of the new push options that it added.

Embed metrics charts in issues - docs

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

Docs: remove extra quote from doc/install/installation.md

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

CE Migration Backport: Add flag to object storage

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

Fix project avatar image in Slack pipeline notifications

Closes #66008

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

Add usage pings for source code pushes

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

Source Code Usage Ping for Create SMAU

Bump Helm to 2.14.3 and kubectl to 1.11.10

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

Expand variables only when needed

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

Rework push mirror retries

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

**Prevention of running 2 simultaneous updates**

Instead of using `RemoteMirror#update_status` and raise an error if
it's already running to prevent the same mirror being updated at the
same time we now use `Gitlab::ExclusiveLease` for that.

When we fail to obtain a lease in 3 tries, 30 seconds apart, we bail
and reschedule. We'll reschedule faster for the protected branches.

If the mirror already ran since it was scheduled, the job will be
skipped.

**Error handling: Remote side**

When an update fails because of a `Gitlab::Git::CommandError`, we
won't track this error in sentry, this could be on the remote side:
for example when branches have diverged.

In this case, we'll try 3 times scheduled 1 or 5 minutes apart.

In between, the mirror is marked as "to_retry", the error would be
visible to the user when they visit the settings page.

After 3 tries we'll mark the mirror as failed and notify the user.

We won't track this error in sentry, as it's not likely we can help
it.

The next event that would trigger a new refresh.

**Error handling: our side**

If an unexpected error occurs, we mark the mirror as failed, but we'd
still retry the job based on the regular sidekiq retries with
backoff. Same as we used to

The error would be reported in sentry, since its likely we need to do
something about it.