Update button variants, add modals, and improve semantics of the markup

Changelog: changed

Milestone widget for Issue and MR page sidebars [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!63722

Reduce space needed for merge request diff commits

See merge request gitlab-org/gitlab!63669

Update dot style in DORA lead time graphs

See merge request gitlab-org/gitlab!65555

Add user_cap column to namespace_settings

See merge request gitlab-org/gitlab!65470

Revert  gitlab-shell version bump

See merge request gitlab-org/gitlab!65667

Fix populate latest pipeline ids background migration

See merge request gitlab-org/gitlab!65280

Add period to end of email sentence

See merge request gitlab-org/gitlab!65610

Changelog: added

Fix LFS objects not downloading with Bitbucket

See merge request gitlab-org/gitlab!65380

This reverts merge request !65625

Fix location of settings for cleanup policies

See merge request gitlab-org/gitlab!65596

Add developer docs for the attribution panels

See merge request gitlab-org/gitlab!64805

Cache entities for compare API [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!64418

Improve upgrade versions details

See merge request gitlab-org/gitlab!65641

Nest start and end event identifiers in VSA API

See merge request gitlab-org/gitlab!65395

Docs for resetting Patroni state in Consul

See merge request gitlab-org/gitlab!64733

Remove date from Seat Link data fields

See merge request gitlab-org/gitlab!65190

Catch Git::CommandError in Branches::CreateService

See merge request gitlab-org/gitlab!64727

Display correct label for named-list report types

See merge request gitlab-org/gitlab!65507

Previously attempting to download LFS files with Bitbucket via a project
import would result in a 401 error. This happened because Bitbucket
returns a `header` payload that should be included in the HTTP GET
request. As described in
https://github.com/git-lfs/git-lfs/blob/main/docs/api/batch.md, we need
to include this with the request for the download to succeed.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/335123

Changelog: fixed

Fix nesting of child pipeline artifacts downloads

See merge request gitlab-org/gitlab!65649

Fix ProtectedEnvironments::SearchService in dev

See merge request gitlab-org/gitlab!65643

Remove ff `sidebar_refactor` from views and remove flag [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!64384

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65190
EE: true

Update tests for snippets to support default branch

See merge request gitlab-org/gitlab!65552

Edited Cron example to reflect accurately

See merge request gitlab-org/gitlab!65642

Doc: Add context commits documentation

See merge request gitlab-org/gitlab!65236

BulkImports: Remove unnecessary transform from GroupAvatar

See merge request gitlab-org/gitlab!65578

The table merge_request_diff_commits stores the names and Emails of
commit authors and committers. This data is stored as-is. This means
that if I push 10 commits, GitLab stores my name and Email address 20
times: 10 times for the author details, and 10 times for the committer
details.

This commit adds a set of migrations and code changes to resolve this
problem. Instead of storing names and Emails for every occurrence, we'll
store a unique set of names and Emails in a separate table. The table
merge_request_context_commits in turn has two new columns:
commit_author_id and committer_id.

When creating rows for merge_request_context_commits, we take the author
and committer details and try to find an existing row in the newly
added table. If no row exists, one is created.

The resulting setup is such that given a name and Email pair of (X, Y),
we only store a single occurrence of that pair. This reduces the amount
of space necessary to store all this information. Based on our findings
in https://gitlab.com/gitlab-org/gitlab/-/issues/331823, we estimate
that over 95% of the data currently stored is duplicate data. For
GitLab.com, we estimate this will translate to roughly 500 GB of data we
no longer need to store.

The migration process for GitLab.com will likely take around two weeks,
based on our estimates discussed in
https://gitlab.com/gitlab-org/gitlab/-/issues/331823#note_595865070. The
exact time may differ based on how lucky (or not) we get, and the exact
number of rows that have to be migrated.

See the following issues for more information:

- https://gitlab.com/gitlab-org/gitlab/-/issues/331523#note_583654940
- https://gitlab.com/gitlab-org/gitlab/-/issues/331823

Changelog: performance

This commit updates the data point style on lead time graphs (both
project and group-level) to always render a blue dot. This makes it
easier to see isolated data points on the graphs.

Changelog: changed
EE: true

Add option to force notification on expired subscriptions

See merge request gitlab-org/gitlab!64838

Limit changing security policy project to project owners

See merge request gitlab-org/gitlab!65123