Avoid saving author object in audit_events table

See merge request gitlab-org/gitlab!31456

Since the introduction of `UnauthenticatedAuthor` object, failed login
event has been persisted as a serialized Ruby object in DB.

!ruby/object:Gitlab::Audit::UnauthenticatedAuthor

This causes undesirable coupling with application code and hinders
future DB migration.

Switch to backend a11y comparison

See merge request gitlab-org/gitlab!31487

Remove overriding CSS styles on Admin Audit Logs table

See merge request gitlab-org/gitlab!31334

Update docs with new sidebar copy

See merge request gitlab-org/gitlab!31477

- container registry
- package registry

Add ellipsis and tooltip on container registry tag name

See merge request gitlab-org/gitlab!31584

- add tooltip
- add tests

Fix: "Annotations missing from Metric Charts"

See merge request gitlab-org/gitlab!31474

Mark CreateCommitSignatureWorker as idempotent

See merge request gitlab-org/gitlab!31414

Add azure machines for under 1,000 users

See merge request gitlab-org/gitlab!31637

Remove the liquid gem and use gsub instead

See merge request gitlab-org/gitlab!31482

Merge branch '213556-move-the-hashed-storage-checks-to-gitlab-app-check-task-instead-of-gitlab-geo-check' into 'master'

Add hashed storage checks to `gitlab:app:check`

Closes #213556

See merge request gitlab-org/gitlab!31172

Add Rubocop cop to flag keyword arguments usage in Sidekiq workers

Closes #217251

See merge request gitlab-org/gitlab!31551

Add proviso to SCIM Okta config process

See merge request gitlab-org/gitlab!31635

We need to stop polling after we have
received the final report since the report
is not going to change anymore.

We should also stop polling after we
receive an error, so we're not constantly
polling an 500 request.

Backported hashed storage checks to CE and updated documentation to
state that Hashed Storage deprecated in 13.0

Display a star next to `starred` dashboards

See merge request gitlab-org/gitlab!31563

Added Kubernetes support policy

See merge request gitlab-org/gitlab!31318

Add the global var SECURE_ANALYZERS_PREFIX

See merge request gitlab-org/gitlab!28617

This variable helps to setup all Security Products with a single
variable. It has numerous advantages over the previous version:
- The var can be set up in `.gitlab-ci.yml` or in the UI
- That means users can define it at the group level directly if needed
- It flattens the paths used (sometimes it was with /analyzers/,
  sometimes not)
- A single variable can now define all the base paths at once

This change is especially useful for air-gapped environments, where all
the images are generally duplicated locally. Having different prefixes
is creating a lot of plumbing just to get started.

Note that we need to create
registry.gitlab.com/gitlab-org/security-products/secure-bundle before
merging this.

refs gitlab-org/gitlab#209258 and gitlab-org/gitlab#209846

Add Web IDE terminal counts

See merge request gitlab-org/gitlab!31158

When dashboards are fetched with a new `starred` property,
they are displayed with an icon indicating they have been starred.

Document how to pull npm packages from custom registries

See merge request gitlab-org/gitlab!31258

Move publish check to its own method

See merge request gitlab-org/gitlab!31381

Add docs for the query variables from URL feature

See merge request gitlab-org/gitlab!30725

Add metrics users starred dashboard services

See merge request gitlab-org/gitlab!30051

Expose issue iid in alert management alert graphql

See merge request gitlab-org/gitlab!31313

Exposes the issue IID attached to `AlertManagement::Alert`

Add project group and ancestors to group list

See merge request gitlab-org/gitlab!31152

This addresses an issue that arises when the owner of a path is the
group under which the project lives (such as `@gitlab-org` for the
Gitlab project..) Gitlab::CodeOwners::GroupsLoader did not add that
group to the list of groups when attempting to determine ownership. This
list of groups is expanded into a list of users that the user
attempting the action (typically a merge) is compared to. Sinc the
project's group is not added to the group list, its members are not
expanded and are thus missing from the list of owners for a given path.

Additionally, this will look not simply at the immediate group of the
project, but at the entire group tree ancestors to the root group. For
example, if the "merge_service" project is at

gitlab-org/engineering/source_code/merge_service

..then any of these groups would be considerable available for listing
as a code owner without having to be invited to the project:

@gitlab-org
@gitlab-org/engineering
@gitlab-org/engineering/source_code

This address both the proximate cause of
https://gitlab.com/gitlab-org/gitlab/-/issues/216345 but of the
long-requested feature https://gitlab.com/gitlab-org/gitlab/-/issues/32432

Enable  #entry_for_path for sectional CODEOWNERS behind feature flag

See merge request gitlab-org/gitlab!31044

Add project import to group-level audit events

Closes #35855

See merge request gitlab-org/gitlab!31103