Previously the app tracked unique visitors for multiple specific
features owned by the compliance group, but not the aggregate across
all these features. This introduces that aggregate so Compliance group
can better understand whether feature usage is shared or siloed.

Remove duplicate JSON schema matcher

See merge request gitlab-org/gitlab!50727

Delete unused images

See merge request gitlab-org/gitlab!50932

Make Vlad to be DRI for Cloud Native Pages

See merge request gitlab-org/gitlab!50832

Block confidential quick action for test cases

See merge request gitlab-org/gitlab!50460

Change gitlab-ci.yaml to gitlab-ci.yml docs

See merge request gitlab-org/gitlab!50901

Correct extension from 'yaml' to 'yml'.

Tweak list indentation

See merge request gitlab-org/gitlab!50931

Drop temporary index on ci builds

See merge request gitlab-org/gitlab!50961

Hide /confidential quick action
for issues with test case type

We had three JSON schema matchers:

1. `match_schema` - takes a data structure and a path to a schema file.
2. `match_response_schema` - takes a response object and a path to a
   schema file.
3. `according_to_schema` - chained matcher on `be_valid_json`, takes a
   schema literal.

The reason for this is that we wanted to operate on various axes:

1. Are we validating a parsed data structure, or a potentially-JSON
   string?
2. Are we providing a path to a schema file, or a literal data structure
   representing a schema?

Happily, the library we're using already solves problem 1 for us.
https://github.com/ruby-json-schema/json-schema#validation says:

> All methods take two arguments, which can be either a JSON string, a
> file containing JSON, or a Ruby object representing JSON data.

So we just needed to solve concern 2, and we handle that by assuming
that if the schema argument is a string, it's not a JSON string
representing the schema, but a path to a schema file.

To handle the chaining that `according_to_schema` had, we can just use
RSpec's `and` method:

    be_valid_json.and match_schema(build_info_payload_schema)

Adds Tier section to feature proposal

See merge request gitlab-org/gitlab!50835

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

Update Gitaly version

See merge request gitlab-org/gitlab!50953

Clean up second Gitaly process in tests

See merge request gitlab-org/gitlab!50855

Try to find elements before waiting for requests

See merge request gitlab-org/gitlab!50919

Upgrade acts-on-taggable to v7.0.0

See merge request gitlab-org/gitlab!50717

Convert incident_management_list.scss into page specific bundle

See merge request gitlab-org/gitlab!50769

Update Gitaly version

See merge request gitlab-org/gitlab!50942

ci: Only keep relevant files after installing tests dependencies

See merge request gitlab-org/gitlab!49014

Fix styling of merge request dropdown badge styles

See merge request gitlab-org/gitlab!50848

docs: Update jobs' duration in pipelines documentation

See merge request gitlab-org/gitlab!50854

Un-quarantine create project spec

See merge request gitlab-org/gitlab!50925

Add author token filtering support for Test Cases

See merge request gitlab-org/gitlab!50747

Replace minmax with setting min-width

See merge request gitlab-org/gitlab!50881

Move widget rebase state to GraphQL

See merge request gitlab-org/gitlab!50859

Remove ci_pipelines_for_merge_request_finder_new_cte feature flag

See merge request gitlab-org/gitlab!50818

Refactor(opsgenie): remove Opsgenie integration frontend code

See merge request gitlab-org/gitlab!50525

Remove the frontend code for
Opegenie configuration within
Incident management

JiraConnect: Send deployment information

See merge request gitlab-org/gitlab!49757

This adds the deployment module, with support for sending deployment
information on state changes.

Update dependency @gitlab/ui to v25.4.0

See merge request gitlab-org/gitlab!50937

Merge branch '282421-devops-adoption-deeplink-to-adoption-tab-on-the-devops-report-page' into 'master'

Deeplink to Adoption tab on the DevOps Report page

See merge request gitlab-org/gitlab!50169

- Mark tab as active based
on presence of tab query param

Replace mount helper with mount from VTU

See merge request gitlab-org/gitlab!50474

Update marginalia gem to v1.10.0

See merge request gitlab-org/gitlab!50898