Merge branch '35695-comment-appears-in-a-wrong-place-after-changing-diff-view-to-inline' into 'master'

Resolve "Comment appears in a wrong place after changing diff view to inline"

Closes #35695

See merge request !13156

This makes the default sort order for branches 'recently updated' rather than by name.

Closes #26890

See merge request !8666

Fix 500 error when rendering avatar for deleted project creator

See merge request !13110

Merge issuable "reopened" state into "opened"

See merge request !12972

added article from techbeacon on CI

See merge request !10452

Update gitlab_flow.md, Teatro seems to be completely dead, see also…

See merge request !13157

Log web hook execution timeout events

See merge request !13134

Docs: fix HAProxy name and exporter's link

See merge request !13091

Add log messages to clarify log messages about API CSRF token verification failure

Closes #35705

See merge request !13158

Update gitlab_flow.md, Teatro seems to be completely dead, see also https://forum.gitlab.com/t/gitlab-flow-documentation-teatro/7774

Make access level for protected tag factories more compatible with EE

See merge request !13133

When you change the diff view (inline / side-by-side), we set a cookie based on
that new view. When you add a comment, we choose the style to use in the
response based on that cookie.

However, when you have just changed diff style, the request cookie will contain
the old value, so we should use the view param instead.

Resolve "Images in Wiki display have wrong size"

Closes #35691

See merge request !13153

[ci skip]

Fixed the breadcrumb title for help pages

Closes #35679

See merge request !13151

Removed inline JS in shared HAML files

See merge request !13073

Follow-up from "Allow to use cross project pipelines" ver 2

Closes #35282, gitlab-ee#2604, and #35584

See merge request !13102

Having two states that essentially mean the same thing is very much like
having a boolean "true" and boolean "mostly-true": it's rather silly.
This commit merges the "reopened" state into the "opened" state while
taking care of system notes still showing messages along the lines of
"Alice reopened this issue".

A big benefit from having only two states (opened and closed) is that
indexing and querying becomes simpler and more performant. For example,
to get all the opened queries we no longer have to query both states:

    SELECT *
    FROM issues
    WHERE project_id = 2
    AND state IN ('opened', 'reopened');

Instead we can query a single state directly, which can be much faster:

    SELECT *
    FROM issues
    WHERE project_id = 2
    AND state = 'opened';

Further, only having two states makes indexing easier as we will only
ever filter (and thus scan an index) using a single value. Partial
indexes could help but aren't supported on MySQL, complicating the
development process and not being helpful for MySQL.

So the behaviour would be similar in CE and EE

Use `:empty_project` where possible in feature specs

See merge request !13118

Remove Mattermost team with GitLab group

Closes #30023

See merge request !11362

Global nav (9.0) UI improvement

Closes #34921

See merge request !12772

Support the fact that Gitaly uses bundler

See merge request !13135

[Backport from EE] Refactors GitPushService spec code

See merge request !13148

Backport some recent changes related to LDAP from EE

See merge request !13119

This reverts commit 5ec3b63bfc6f341df040ae08be4858c7181bcacf.