Fixes rubocop exceptions in tests no 13

- Add spec for supports_canceling?
- Fix pipeline feature spec and add an example
- Fix merge train auto merge service spec
- Consider a build retryable if canceling since
users should not need to wait for the after_script
to run to retry
- Fix cancel pipeline service spec
- Fix the cancel redundant pipelines service spec
- Fix create pipeline service spec
- Fix cancel redundant pipelines worker spec
Fix 2 more specs:
- spec/models/environment_spec.rb
- spec/workers/ci/cancel_pipeline_worker_spec.rb

This reverts merge request !144921

The service_desk_vue_list feature flag is default enabled
so we can delete it now and delete the legacy code

Changelog: other

Project -> Settings -> Repository -> Mirroring repositories -> Add New
was the only usage of this class.

Split feature specs into multiple files since one file was getting
too large and causing intermittent failures.

- Hide title and filter controls when no groups are visible on a Groups page.
- Remove banner on Explore groups page.
- Add illustration when there are no groups found.

Changelog: changed

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/144553

Changelog: fixed

This change introduces a new feature flag to replace the project
runner edit form with a Vue implementation.

Users will see a form that matches the design of the admin and group
runner forms.

This change removes enable_new_sentry_clientside_integration in favor of
enable_new_sentry_integration to have a single feature flag that
defined the sentry compatibility state.

Changelog: other

- Feature was obsoleted in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/73514
  and not removed.
- See https://gitlab.com/gitlab-org/gitlab/-/issues/344079

Merge branch 'security_prevent_ldap_user_password_sign_in' into 'master'

See merge request gitlab-org/security/gitlab!3870

Changelog: security

The original MR(Show admin mode within active sessions view) has
been reverted due to failures:
https://gitlab.com/gitlab-org/release/tasks/-/issues/8332#note_1748203585 on staging-canary.
See discussion https://gitlab.com/gitlab-org/gitlab/-/merge_requests/142158#note_1748221369
It was agreed to implement it in two steps, and this is step one.

Within this MR CurrentUserMode is extend with session parameter and
within load_raw_session only known attributes of ActiveSession
are loaded. This fixes the root cause for the crash within
staging-canary.
In the future new attributes can be added without the risk of a crash
as only known attributes are passed to the constructor.

Add edit pattern for labels widget

Changelog: changed

This is a step towards the feature of supporting the GitLab for Slack
app integration to be configured at group and instance-level.

https://gitlab.com/gitlab-org/gitlab/-/issues/391526

The change adds route, controller and view support for group-level and
instance-level configuration.

The changes are hidden behind a feature flag.

- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144448

Changelog: changed

This MR sets up validation for semantic versioning when releasing a new
vesion of the catalog resource.

* Add migration for adding columns to support parsing of SemVer
* Updates the Versions::CreateService to use `release.tag` for
  versioning
* Updates specs that were not using semantic version, thus testing the
  semantic version validation further
* Quarantines an out of date feature spec

Changelog: added

Use the components from the Environments list page.
Use the existing query.
Update the layout.

Changelog: added

Changelog: changed

Changelog: changed

updated_at is not a good field for sorting, because it is also
updated for non-activity reasons. By changing the sort order to
last_activity_at, the order makes more sense

Changelog: changed

Make setting accessible from UI for changing settings

Add specs for the new application setting in API and model

Use the new setting column value in pipeline service rate limiter

Update documentation to reflect the new setting changes

This is behind the feature flag
ci_rate_limit_downstream_pipelines.

- for setting and using current organization throughout the app.
- using middleware will allow us to make available in api,
  controller and graphql layers
- move away from using our own CurrentOrganization module and use
  the rails provided CurrentAttributes which attaches to threads
  the same way and provides some default tooling.
- see https://gitlab.com/gitlab-org/gitlab/-/issues/437541

Update the page to include tabs,
move deployments list under the 'deployment history' tab,
update the empty state.

Changelog: changed

In Epic https://gitlab.com/groups/gitlab-org/-/epics/9006,
gitaly is removing its reliance on writing out
info/gitattributes. A key step of that is to stop
using ApplyGitattributes() (make it no-op) see MR
https://gitlab.com/gitlab-org/gitaly/-/merge_requests/6573.

ApplyGitattributes() is the RPC call behind copy_gitattributes,
so this MR aims to prepare rails tests for
stopping using ApplyGitattributes().

The purpose of this MR has two folds:

1. with this changes, the rail tests should pass with current gitaly
2. once MR https://gitlab.com/gitlab-org/gitaly/-/merge_requests/6573
is in, the tests should pass with updated gitaly

- Create sidebar with user info
- Group info types
- Move other content to right column
- Add border to readme and activity calendar
- Move activity directly under activity graph

Changelog: changed

Changelog: changed

Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/433130

WIP

Changelog: changed

Changelog: changed

Wikis and repositories no longer allow unlimited
math rendering. It is now controlled by the
`math_rendering_limits_enabled` instance and
group setting.

Changelog: fixed