This commit updates the styling of the
Security & Compliance Carousel to match
the design specs.

Adds the pipeline editor documentation

See merge request gitlab-org/gitlab!51461

A light copy edit for TW style/standards and
rename image to match standards as well.

Merge branch '297201-flaky-spec-in-spec-features-issues-issue_state_spec-rb-issue-state-when-closed-when-clicking' into 'master'

test: Quarantine flaky tests

See merge request gitlab-org/gitlab!51599

Merge branch '297505-flaky-test-ee-spec-features-epics-epic_show_spec-rb-1-5-2-2-1-1-epic-show-epic-actions-when' into 'master'

test: Quarantine flaky tests

See merge request gitlab-org/gitlab!51591

Rotation controls styling cleanup

See merge request gitlab-org/gitlab!51353

Improve error messages when CI blob is not loaded

See merge request gitlab-org/gitlab!51584

Fix BoardCardLayout component and use gl utility [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!51430

Force CI schema URL to be absolute

See merge request gitlab-org/gitlab!51479

Signed-off-by: Rémy Coutable <remy@rymai.me>

Add code testing to some workers

See merge request gitlab-org/gitlab!51449

Track CI template usage data by default

See merge request gitlab-org/gitlab!51391

In WebIDE, when closing a file, switch to the new one before closing the active one

See merge request gitlab-org/gitlab!51483

To avoid disposing the repo_editor component, we have to
make sure we always have an active file if we have any
open files at all. Othewrwise the whole component gets
diposed that triggers all possible events and unnecessary
processing related to diposing the old one and setting up
the new editor instance

Update toggle button in repo general settings

See merge request gitlab-org/gitlab!51036

Adding benefits of feature flags section

See merge request gitlab-org/gitlab!49962

- On the feature flags process page there were a lot of examples of the
  cost of feature flags, but it the reasons we want to use feature flags
were not clearly spelt out. This change adds a section about the
benefits of using development type feature flags.

These workers should have the code_testing feature category.

This change improves usability for users when the yml file
is not defined, it does this by changing the error message
and hides controls that don't work in the editor.

Add CI config fields to lint tab

See merge request gitlab-org/gitlab!50754

Bump labkit-ruby gem version

See merge request gitlab-org/gitlab!51582

Remove feature flag that enables squash commit persistence

See merge request gitlab-org/gitlab!51074

Merge branch '297507-flaky-test-spec-features-projects-releases-user_creates_release_spec-rb-50-user-creates' into 'master'

test: Quarantine flaky tests

See merge request gitlab-org/gitlab!51597

Clean up Tooling::TestFileFinder

See merge request gitlab-org/gitlab!48650

Tooling::TestFileFinder has been replaced
with `test_file_finder` gem.

Extract housekeeping methods to concern

See merge request gitlab-org/gitlab!51564

Rolldown issue and merge request templates in the group hierarchy

See merge request gitlab-org/gitlab!46222

Signed-off-by: Rémy Coutable <remy@rymai.me>

Link GitLab Review Workload Dashboard in Danger Reviewer Roulette

See merge request gitlab-org/gitlab!51459

Just in case folks want more options.

Signed-off-by: Rémy Coutable <remy@rymai.me>

ci: Test low-level database library code against PG12 [RUN ALL RSPEC]

See merge request gitlab-org/gitlab!50862

This change adds a few fields from the CI config that are now available
in the GraphQL API such as `script` and `allow_failure`.

Restore accidentally removed index

See merge request gitlab-org/gitlab!51438

Updates graphql linter implementation

See merge request gitlab-org/gitlab!50664

* Replaces CiConfig with ::Gitlab::Ci::Lint, rather than using the
YAML Processor
* Adds job needs to the Lint processor
* Adds new fields to the CiConfigJobType
* Updates specs
* Adds docs and schema

In order for workers loaded from `data://` as the
ones loaded by monaco, we use absolute URLs to fetch
schema files, hence the `location.origin` reference.
This prevents error: "Failed to execute 'fetch' on 'WorkerGlobalScope'"