Update docs on how to enable partial clones

See merge request gitlab-org/gitlab!19397

Fix Bitbucket Cloud importer pull request state

Closes #35746

See merge request gitlab-org/gitlab!19734

Remove unnecessary SQL queries from avatar requests

See merge request gitlab-org/gitlab!19383

Fix feature flag for license list page

See merge request gitlab-org/gitlab!19702

Explicitely call Feature.enabled? to default to false
on all instances until feature is completed

Upgrade redis-store and redis-activesupport

See merge request gitlab-org/gitlab!19678

Allow container scanning to run offline

See merge request gitlab-org/gitlab!19161

Vue file listing refactor load README files

Closes #35638

See merge request gitlab-org/gitlab!19689

Due to e404c311, all pull requests are
created in the `opened` state because assigning the `state` parameter
when creating a `MergeRequest` no longer works. To fix this, define the
`state_id` in the `initalize` step to ensure state_machine has the
right value to use.

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

Resolve "Make snippet list easier to scan"

Closes #31964

See merge request gitlab-org/gitlab!19490

Add max width on manifest file attachment input

Closes #28350

See merge request gitlab-org/gitlab!19028

Remove existence check from ProjectUrlConstrainer

See merge request gitlab-org/gitlab!19412

Add variables for DIND-less implementation to the SAST docs

See merge request gitlab-org/gitlab!19537

Note that admin rights  are needed by the feature flag API

See merge request gitlab-org/gitlab!19475

Instead of excluding XHRs for these actions, we only want to perform
them when we're serving an HTML page. If we're serving an image or an
Atom feed, they are mostly useless:

1. Gon variables can't be used by an image.
2. Redirects won't be seen if an image is embedded in another page.

UploadsActions memoizes the result of `#find_model` in `#model`. That
means that if we call `#find_model` first, we'll run the query twice. As
`#model` is memoized, we don't need the `before_action` at all anyway.

Change blob view edit styling

Closes #30810

See merge request gitlab-org/gitlab!19566

Use group for Frontend code owners

See merge request gitlab-org/gitlab!19764

Rubocop Cop to auto-correct all *_any_instance_of spec helpers

See merge request gitlab-org/gitlab!19164

Add test isolation to FE testing guide

See merge request gitlab-org/gitlab!19368

Resolve "Increase gitlab-shell review-app CPU and timeout"

Closes #35796

See merge request gitlab-org/gitlab!19739

Improve `/-/health` to look at state of master

See merge request gitlab-org/gitlab!19441

1. This moves blackout period to `shutdown: blackout_seconds:`
1. This moves a blackout period logic to `LifecycleEvents`
1. This makes `web_exporter` to use lifecycle events
   for blackout period
1. This adds additional health check to look at state
   of master process
1. Exempt `/liveness` and `/readiness` from Rack Attack
1. Make `/liveness` and `/readiness` to not hit DB/Redis
1. Optimise Rack Attack handling

Move DAST reports logic for the Merge Request widget to the backend

See merge request gitlab-org/gitlab!18660

Add dast_report to authorized endpoints

Update merge_request.rb#has_dast_reports? to check on dast_reports

Update FactoryBot params, use frozen_string_literal: true

Update specs according to the new fixture

Resolve "Rename <ApolloMutation> component to <apollo-mutation>"

See merge request gitlab-org/gitlab!19728

This increases the maintainability of the Frontend group owners by
utilizing the group `gitlab-org/maintainers/frontend`

API endpoint to list the packages of a group

See merge request gitlab-org/gitlab!18871

This API method is similar to the one listing packages within a project
but for the group level

Rename the existing packages API class to make it more explicit that it
  is for the project level
Add the packages API class for the group level
Add the related access checks in `GroupPolicy`
Refactor packages API specs so that both levels share a common examples
Add the docs for the new group level API method

Move error_tracking state closer to component

See merge request gitlab-org/gitlab!19542

Rather than passing a bunch of store data to error_tracking via
the parent component, use Vuex methods in the component directly
This means changes to the error tracking form won't also require
props changes and changes to the parent component

This cop auto-correct automatically all the references in RSpec as:
- expect_any_instance_of -> expect_next_instance_of
- allow_any_instance_of -> allow_next_instance_of

At the moment it's disabled because I'm going to correct all the
offenses in different merge requests.