Replace mountComponent with mount

See merge request gitlab-org/gitlab!52929

Explain Gitaly Cluster components

See merge request gitlab-org/gitlab!51946

Add front matter for 3 new pages

See merge request gitlab-org/gitlab!52930

These pages need to be tracked by the technical writing team.
Add front matter to do so.

Deal with spelling issues throughout docsets

See merge request gitlab-org/gitlab!52927

Create the update form for compliance frameworks

See merge request gitlab-org/gitlab!52479

Deal with spelling issues in multiple ways. Add some words to the
spelling exceptions list. Fix misspellings. Turn off spellchecking on
things that shouldn't be in the exceptions list, but we also can't
remove.

Don't require a bucket if object storage is disabled for a type

See merge request gitlab-org/gitlab!52750

Extract Roadmap filtering to a mixin

See merge request gitlab-org/gitlab!52793

Hack `Prependable` class methods for `override`

See merge request gitlab-org/gitlab!52419

Add API for generating changelogs in GitLab

See merge request gitlab-org/gitlab!52116

Fix capitalization

See merge request gitlab-org/gitlab!52853

Migrate health status dropdown to use gitlab ui

See merge request gitlab-org/gitlab!52273

Previously if a user enabled consolidated settings then selectively
disabled some object storage types, they were still required to set a
bucket name for that object type. For example:

1. Enable consolidated object storage
(https://docs.gitlab.com/ee/administration/object_storage.html).

2. Configure the artifacts object storage with the below:

```
gitlab_rails['object_store']['objects']['artifacts']['enabled'] = false

gitlab_rails['artifacts_enabled'] = true
```

Reconfigure GitLab and you see this error:

```
Object storage for artifacts must have a bucket specified
```

Since the previous workaround would be to set a dummy bucket name, this
change skips assigning consolidated settings if object storage has been
disabled for a specific type.

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

Merge branch '227349-package-registry-expand-the-filter-and-sort-functionality-on-the-package-registry-list-view' into 'master'

Redesign the search UI for the package list

See merge request gitlab-org/gitlab!52575

- source
- tests
- snapshots

Fix rename column concurrently

See merge request gitlab-org/gitlab!52032

Forbid git pushes to group wikis when repo is read only

See merge request gitlab-org/gitlab!52801

Fix tier for custom branch name for groups

See merge request gitlab-org/gitlab!52632

`ActiveSupport::Concern` uses an unusual way to chain class methods,
which does not exactly follow how Ruby chains the classes.

In particular, it's like Concern reinvents the object model and
builds the ancestors chain in runtime, rather than at the compile time.
This for sure introduced a lot of culprits.

This fix is aiming for restoring the class methods for the module
which is defining the class methods. To be specific, consider this case:

``` ruby
module Base
  extend ActiveSupport::Concern

  class_methods do
    def f
    end
  end
end

module Derived
  include Base
end
```

What would you expect for this?

``` ruby
Base.f    # => NoMethodError
Derived.f # => nil
```

With this hack, it'll allow `Base.f` to work, which can make `override`
check for class methods. Before this hack it'll not work due to this
disparity.

Since so far the only place we really need this is when we're checking
`override` with those class methods, we don't have to take the risk to
change how it works in production, but just how we check `override`.

This hack is needed for `override` because we're checking `prepend` at
where it's defined, not at where it's eventually included into a class,
and that's where Concern does the magic.

If one day we can stop using `ActiveSupport::Concern`, and just do
plain old good Ruby, we'll be free from all those wild hacks.

See original bug report: https://gitlab.com/gitlab-org/gitlab/-/issues/23932

Use backend code quality diff for MR widget when feature flag is enabled

See merge request gitlab-org/gitlab!52365

Remove avatar of the blocked user

See merge request gitlab-org/gitlab!52051

When a user is blocked for violating the terms of service on gitlab.com, their profile and history is no longer accessible, but their avatar is still visible.

Add `gl-button` to promotion buttons on issue sidebar

See merge request gitlab-org/gitlab!51287

This updates the views to be pajamas compliant

Adding GlAlert component

See merge request gitlab-org/gitlab!52217

This updates the error alert banner on the new feature flag form
and edit feature flag form to just warning.

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

Update group:access docs, to replace "STARTER*" Tiers

See merge request gitlab-org/gitlab!52733

Apply new GitLab UI for input field in admin/appearance

See merge request gitlab-org/gitlab!52409

Word and line reviews for Create documentation

See merge request gitlab-org/gitlab!52852

More reviews of words and lines, to deal with issues flagged by our
linting system.

Use vue test utils in MR Widget Status Icon spec

See merge request gitlab-org/gitlab!52493

Apply new GitLab UI for input fields in the file editor

See merge request gitlab-org/gitlab!52461

Delete extra `using RSpec::Parameterized::TableSyntax` references

See merge request gitlab-org/gitlab!52832