Fix missing .btn-success class on the following buttons:
* 'Create milestone' button
* Secondary button on profile tabs

`btn-create` was an old class which was was removed in !23232
and replaced with `btn-success`,
but these two seem to have been missed in the process.

git-user-related local test failures

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

Remove usage of gitlab-shell gitlab-keys script

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

Fix snippets API not working with visibility level

Closes #66050

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

Fixed embedded metrics tooltip inconsistent styling

Closes #65063

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

Remove incorrectly structured url

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

Remove unnecessary CSS class

Closes #66163

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

Standardize use of `content` parameter in snippets API

Closes #66673

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

Resolve "Issue due notification emails are threaded incorrectly"

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

Add E2E spec to ensure that issue closes with commit message

Closes gitlab-org/quality/testcases#15

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

Add E2E spec to test that issue closes with commit message

Set dast job to extend .review-only

Closes #66718

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

Update documentation screenshot

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

Fix capitalization in more docs

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

Fix capitalization in docs for works like GitLab, Git
Omnibus, etc

Make Auto DevOps requirements easier to read

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

Utilize the auto repair functionality of system checks.

This check is being removed from gitlab-shell as the file
is now being managed by gitlab-rails.

This is the same as gitlab-shell's default. This is to ensure
that it's always set.

It needs to be the same as gitlab-shell's default because we
don't set a default value in omnibus-gitlab. If users don't
set the value of that config in their install and they upgraded,
we must ensure that it's still going to point to the same
authorized keys file.

Simplify internal post receive messages

Closes #59808

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

New project milestone primary button

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

This reverts commit af5242ecb682189c5d8276e1ab1ffe5ce844f2e5.

Remove checkbox styling

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

Resolve "Migrate spec/javascripts/vue_mr_widget/components/states/mr_widget_auto_merge_failed_spec.js to Jest"

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

Merge branch '56130-operations-environments-shows-incorrect-deployment-date-for-manual-deploy-jobs' into 'master'

Show correct deployment date for a manual job

Closes #56130

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

Mention Jest in testing guide docs

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

- Reword relationship between Jest/Karma/Jasmine
- Prefer inline URLs, per the [docs]

[docs]: https://docs.gitlab.com/ee/development/documentation/styleguide.html#links

Merge branch '62284-follow-up-from-resolve-api-to-get-all-project-group-members-returns-duplicates' into 'master'

Resolve "Follow-up from "Resolve "API to get all project/group members returns duplicates"""

Closes #62284

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

There was some confusion over whether `code` or `content` is the right
parameter for snippets. Internally, the database stores
`content`. However:

1. Project snippets use `code`. `code` gets remapped in `content` in
`lib/api/project_snippets.rb`.

2. Personal snippets use `content`.

To unify these APIs, allow an alias of `content` to work for project
snippets.

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

When a restricted visibility level of `private` is set in the instance,
creating a snippet with the `visibility` level would always fail.
This happened because:

1. `params[:visibility]` was a string (e.g. "public")
2. `CreateSnippetService` and `UpdateSnippetService` only looked
   at `params[:visibility_level]`, which was `nil`.

To fix this, we:

1. Make `CreateSnippetService` look at the newly-built
   `snippet.visibility_level`, since the right value is assigned by the
   `VisibilityLevel#visibility=` method.
2. Modify `UpdateSnippetService` to handle both `visibility_level` and
`visibility` parameters.

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

Update a few redirected links

Closes #64285

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

Add warnings to performance bar response

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