Topic title edits

See merge request gitlab-org/gitlab!54999

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/300312

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/54999

Add snapshot testing docs

See merge request gitlab-org/gitlab!52508

Add some documentation on
using snapshots at gitlab.

Create service for assigning policy project

See merge request gitlab-org/gitlab!54812

Provide branch information from dastProfiles [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!55015

- Add dast_branch_selection ff disabled by default
- Add new field and associated type
- Add new policy
- Add new model

Docs: Correct role levels required for Release CRUD

See merge request gitlab-org/gitlab!55367

Current permission docs are incorrect when it comes to deleting a
Release object in a project.

When originally added, the permission was only given to maintainers or
higher to be able to delete a Release:
Commit 8f1e96c8
from ~2018

This change corrects the permissions table and updates the API
documentation to mention the roles required when creating,
editing/updating, or deleting a Release.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/219392

Show subscription expiration banner only for top-level group owners

See merge request gitlab-org/gitlab!54908

Remove obsolete DOMContentLoadedEventListener

See merge request gitlab-org/gitlab!55054

Clarify version text formatting

See merge request gitlab-org/gitlab!55340

Linking to user following documentation

See merge request gitlab-org/gitlab!55416

Enable RSpec/MultipleMemoizedHelpers by default

See merge request gitlab-org/gitlab!55211

Remove pipeline editor feature flag [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!54971

The Pipeline Editor is no longer behind a feature flag,
we remove all related code including tests.

Add a vale rule to check for usage of "master"

See merge request gitlab-org/gitlab!55148

We should use default branch or main branch, instead
of master

Fix(oncallschedules): update grid start and midnight edge case

See merge request gitlab-org/gitlab!55081

Update the grid start time and allow
for midnight shift edge case
in weekly grid draw for shifts less
than 24 hours

NotificationsHelper: Remove unused helper methods

See merge request gitlab-org/gitlab!55346

Expose VSA stage event descriptions

See merge request gitlab-org/gitlab!54954

Revisions to the examples area

See merge request gitlab-org/gitlab!55397

Tidy up the phrasing and formatting of the examples area.

Fix the nature of FactoryBot traits that create associations of Namespace [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!55160

Add empty state inside pipeline editor section

See merge request gitlab-org/gitlab!55227

This adds an empty section with no CTA inside the pipeline
editor if there is no file to edit. At a later date, we
are going to add the option to start working even without an
existing file.

Align heading style with subheadings in markdown

See merge request gitlab-org/gitlab!55284

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/55284

Group migration: User-selectable page size

See merge request gitlab-org/gitlab!54638

Set default MR title/description to first multi-line commit

See merge request gitlab-org/gitlab!52984

Show which reviewers have approved an MR

See merge request gitlab-org/gitlab!54365

This updates the reviewer sidebar widget to display
an `approval-solid` icon  next to reviewers who have
approved the MR.

Migrate project cycle analytics template to vue

See merge request gitlab-org/gitlab!54882

Auto-enable admin mode on privileged environments

See merge request gitlab-org/gitlab!53015

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/300479

When creating a merge request, the behaviour of the prefilled title and
discription is different than the behaviour of squashed commit messages.

For squashed commit messages, the behaviour is described in the
[docs](https://docs.gitlab.com/ee/user/project/merge_requests/squash_and_merge.html#overview)
as

> Taken from the first multi-line commit message in the merge.

However, for merge requests, the current behavior is to use the branch
name.  This commit sets the prefilled MR title/description to the first
multi-line commit in the MR, if applicable.  Otherwise falling back to
the previous behaviour.