This should make the suite pass regardless of the state of the
`security_configuration_redesign(_ee)?` feature flags.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/336472.

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

Also note the [follow up][1] to further improve the reactivity
approach for initializing the Content Editor.

[1]: Move Content Editor loading and initialization to a Vue component

- source
- test

Changelog: fixed

- Add compliance framework to entity
- Add compliance framework label component to group item
- Add compliance framework to store
- Create tests

Changelog: added
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/66819
EE: true

We need to handle translation of errors returned by the papaparse
csv parsing library and package up a reusable component for
displaying them. This can be resued in the  upcoming diff viewer.

Changelog: added

Participant avatars in merge requests used a generic alt tag
("user avatar") instead of the user's name, which meant screenreaders
repeated the phrase "user avatar" over and over, instead of useful
text.

Changelog: changed

This change fixes the help page URLs in the job
sidebar for "Set maximum job timeout for a runner"
to the correct page.

Changelog: fixed

This change adds the possibility for users to reset their registration
token in their group.

When an instance admin changes the user cap settings for
signups, they will now see the number of pending users that
will be automatically approved (if applicable)

Changelog: added
EE: true

Changelog: added
EE: true

Refactor Content Editor spec files to use
simpler import statements to include extensions

Move node and mark serializers out of the
tiptap extension files. Define the serializer
config in the Markdown Serializer factory
module

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

Display correct edit buttons when viewing binary files

The data-method attribute was removed by our config of
DOMpurify since we are using v-safe-html. Since this
is trusted input (comes from our own code), we should
allow these attributes for Rails remote link functionality.

Changelog: fixed

Due to a bug in DOMPurify, we had to implement
potentially dangerous data-* attribute sanitization using
hooks. These checks can be removed now as they are
no longer needed.

This will allow v-safe-html to configure if it should allow
these attributes for inputs that are safe.

This reverts changes introduced in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65301

Changelog: changed

Only init the app for now

As part of https://gitlab.com/groups/gitlab-org/-/epics/5759 we're
preparing the GitLab application to handle connections to multiple
databases. As such we want to improve our observability to understand
these multiple databases.

This MR just adds the database name to the performance bar details.

Unfortunately the default rails database config name is `primary`.
Eventually we will force this to be `main` and it will be distinct from
the new `ci` database. This does create a little bit of confusion now as
we also use the words `primary/replica` to distinguish between our
read/write and read-only database servers. This means you may see
"Replica" next to "Config name: primary" which could be confusing. I
hope that the usage of "Config name" should help to disambiguate. I have
also used a feature flag to be less disruptive.

Change the color variant for green from 608b2f to 366800

Changelog: changed

Gitorious was removed as a project import
option in 8.11. This removes the logos that are
no longer in use.

Changelog: other

It is added both as filtered search value and token. This
allows users to see labels as the selected token and they
can even select more labels in the filter bar if needed.

We are currently not using `fetchLabels` since the backend
for this is not ready yet.

Changelog: changed
EE: true