Work around vue/one-component-per-file violations

See merge request gitlab-org/gitlab!51626

Update Workhorse to v8.60.0

See merge request gitlab-org/gitlab!51965

Add improved copy and rename the files

See merge request gitlab-org/gitlab!51757

Fix top border-radius of the login box

See merge request gitlab-org/gitlab!51950

Apply GitLab UI button styles to button _blank_state_ee_trial

See merge request gitlab-org/gitlab!51778

Move Danger code from lib/ to tooling/ [RUN ALL RSPEC]

See merge request gitlab-org/gitlab!51566

These were added because of Rails eagerload.
These files are now moved out of Rails eagerload path,
so the conditionals are not necessary.

Test deprecation of `text/plain` on all endpoints

See merge request gitlab-org/gitlab!46133

This reverts commit 3211640a.

Remove custom Danger check for frozen_string_literal comments

See merge request gitlab-org/gitlab!51930

Add metric definitions to Product Intelligence Dangerfile

See merge request gitlab-org/gitlab!52073

Add basic components for packages settings

See merge request gitlab-org/gitlab!51883

- source
- test
- snapshots

Add missing test coverage on Group API spec

See merge request gitlab-org/gitlab!52055

Migrate EE MrWidgetOptions spec to @vue/test-utils

See merge request gitlab-org/gitlab!51926

Fix a Bundler deprecation

See merge request gitlab-org/gitlab!51995

Add auto-fix Label

See merge request gitlab-org/gitlab!50657

We need to assign a special label to identify bot's MRs

This is redundant with Rubocop's Style/FrozenStringLiteralComment cop,
which we didn't have enabled when this was introduced.

To preserve the same behaviour we also:

- Switch to `EnforcedStyle: always_true`, to forbid `false` values.
- Replace the wildcard list with an explicit list of all violations,
  so we still catch all newly added files.

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

[RUN ALL RSPEC] Print out remaining deprecations

See merge request gitlab-org/gitlab!51820

Fix ActiveRecord::Records flaky spec

See merge request gitlab-org/gitlab!51909

Update links to new issues to fix "Maximum number of comments exceeded" error - 5 of 5

See merge request gitlab-org/gitlab!52063

Update links to new issues to fix "Maximum number of comments exceeded" error - 4 of 5

See merge request gitlab-org/gitlab!52062

Add merge_request_refs_cleanup feature flag

See merge request gitlab-org/gitlab!51558

Update links to new issues to fix "Maximum number of comments exceeded" error - 3 of 5

See merge request gitlab-org/gitlab!52058

Fix crash in Puma validation initializer

See merge request gitlab-org/gitlab!52072

Fix JS error on welcome page

See merge request gitlab-org/gitlab!52022

The input field for "other" role only gets rendered when the feature
flag is active. Therefore we need to check if it exists when we receive
a `change` event on the select box.

We are experiencing performance issues with the merge request
refs cleanup functionality on production and some customers
instances. This became more visible when we started backfilling
`MergeRequest::CleanupSchedule` records for old merge requests.

Disabling the worker and scheduler for now behind a feature flag
so we can test the feature once we improve it's scheduling logic
before enabling it on other instances.

Step 1 - Clean up `commit_sidebar/form_spec` and commit constants

See merge request gitlab-org/gitlab!51816

Merge branch '297500-flaky-test-spec-features-merge_request-user_closes_reopens_merge_request_state_spec-rb-87' into 'master'

Quarantine flaky tests

See merge request gitlab-org/gitlab!51997

Fix rspec-db-library-code-pg12 job in gitlab-foss

See merge request gitlab-org/gitlab!52047

It was using a method before it was defined, which did
not show up in unit tests.