Fix broken contribution_analytics_spec test

Closes #220255

See merge request gitlab-org/gitlab!33813

Update reduce repo size docs to use `git filter-repo`

Closes #33472 and #219718

See merge request gitlab-org/gitlab!33576

Harden flipper feature.get access

Closes #220008

See merge request gitlab-org/gitlab!33590

Pass hard delete option to snippets bulk destroy

See merge request gitlab-org/gitlab!33520

RSpec zero monkey patching mode

See merge request gitlab-org/gitlab!33721

Adjust text expectations due to UI changes
See https://gitlab.com/gitlab-org/gitlab/-/issues/220255
And https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33535

Geo Package Files - Initialize

See merge request gitlab-org/gitlab!33425

Add built in variable called __range

See merge request gitlab-org/gitlab!33521

Remove leftover from DuplicateSpecLocation

See merge request gitlab-org/gitlab!33693

Restructure contributing information

See merge request gitlab-org/gitlab!33473

Docs: more spelling fixes (again!)

See merge request gitlab-org/gitlab!33777

More words that should not trip up the spell checker.

The documentation now recommends git filter-repo. In-application help
links should be consistent.

Git filter-repo produces a commit-map file that does not have a file
extension. This prevents it from being uploaded without renaming the
file. Removes file type validation to permit upload.

Purging data from a Git repo can be useful for different reasons,
including making cloning faster, or reducing repo size on the GitLab
server. The first is easy, the second is hard.

Documentation has been rewritten to use `git filter-repo` which is the
leading repo rewriting tool for this application, and is recommended by
the Git project.

Documentation now also provides workflow for pruning all kinds of refs,
including refs/keep-around/* which was not documented. This meant
purging files was incomplete from disk use perspective on the GitLab
server.

References to BFG have been removed.

Docs: Add Monitor stage as owner of these docs

Closes #220197

See merge request gitlab-org/gitlab!33773

Change approved to merged in Contribution Analytics

See merge request gitlab-org/gitlab!33535

Previously Contribution Analytics listed "approved" merge requests,
which meant merged. That use of non-standard terminology was confusing
to users, so this changes it to "merged" for clarity.

RSpec zero monkey patching mode

See merge request gitlab-org/gitlab!33724

Grammar fix (missing word)

See merge request gitlab-org/gitlab!33617

RSpec zero monkey patching mode

See merge request gitlab-org/gitlab!33733

Update user model specs for delegated methods

See merge request gitlab-org/gitlab!33798

RSpec zero monkey patching mode

See merge request gitlab-org/gitlab!33723

Add optional expires_at param to Users API endpoint Add SSH key

See merge request gitlab-org/gitlab!33633

Add project audit events API

Closes #219238

See merge request gitlab-org/gitlab!33155

Always use external tracker to cross reference external issues

See merge request gitlab-org/gitlab!33263

Add issueLinks field to Vulnerability type

See merge request gitlab-org/gitlab!33173

fix has to have and capital NOT to lowercase not typos

See merge request gitlab-org/gitlab!33788

Decouple wiki controller from projects

See merge request gitlab-org/gitlab!32960

Generate metrics on commit

Closes #215166

See merge request gitlab-org/gitlab!32668

Skip configure rake task if container registry is misconfigured

See merge request gitlab-org/gitlab!33631

Update GitLab UI/SVG

See merge request gitlab-org/gitlab!33774

RSpec zero monkey patching mode

See merge request gitlab-org/gitlab!33730

Merge branch '219151-follow-up-from-fallback-to-lowest-visibility-level-in-snippet-visibility-radio' into 'master'

Resolve "Follow-up from "Fallback to lowest visibility level in snippet visibility radio""

Closes #219151

See merge request gitlab-org/gitlab!33388