Backport ee 7203 sticky logs topbar

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

Fixes diff discussions not being fully removed

Closes #53317

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

Fix extra merge request versions created from forked merge requests

Closes #53153

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

Wait for push before checking for new commit

Closes gitlab-org/quality/staging#14

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

This fixes a bug where a discussion on a none changed line
would not get fully removed and therefore leave the comment row
empty. This was caused by the discussiob being added
to the right when it shouldnt of been

This also fixes a very rare edge case where discussions would get added
twice to diff lines causing a Vue rendering warning

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

Fix #53298 JupyterHub restarts should work without errors

Closes #53298

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

Fix Review Apps testing guide

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

Renaming Secret Variables in the codebase

Closes #49629

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

Adding tests for filtering activities/comments in issues

Closes #51889

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

Fix problem with spec that showed up in EE merge

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

docs: Add deprecation notice for renamed licensed feature

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

Added a note about machine types

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

When a forked merge request was created with the same branch name as the
target name, MergeRequests::RefreshService would always create a new
diff even though nothing had changed. For example, on GitLab.com:

1. There were a number of merge requests in the gitlab-ce and www-gitlab-com
projects that had old merge requests from the community.
2. These merge requests originated from forked projects and used the
source branch master.
3. When someone pushed to master in the main repository, MergeRequests::RefreshService
would see that master matched the merge requests in question and generated a new
diff.
4. This led to an explosion of merge request diffs and slowed down the "Changes"
tab considerably.

This change alters MergeRequests::RefreshService so that it will only
refresh the diff if the merge request's source project and branch
match. Otherwise, the refresh will only happen if a pushed commit
contains a commit relevant to the existing merge request.

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

Update gitlab-ui to 1.9.0

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

Remove mousetrap-rails gem

Closes #53270

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

Make new merge request URL more friendly when pushing code

Closes #53012

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

Add e2e test to push using a private token

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

Changes from docs review

Update moment to 2.22.2

Closes #53273

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

Update GitLab Pages to v1.3.0

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

Replace deprecated uniq on a Relation with distinct

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

Rename 'sast_container' licensed feature

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

Upgrade whitequark/parser to 2.5.3.0

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

Delete job_spec.js

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

Tests pushing over HTTP(S) using a personal access token

Truncate milestone title on collapsed sidebar

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

[11.4] Fix Token lookup for Git over HTTP and registry authentication

See merge request gitlab/gitlabhq!2577