Also added an ldap trait to the omniauth_user factory.

Build a test to compare service ping output with output of the values from SQL generated

See merge request gitlab-org/gitlab!81002

Mirroring test fixes

See merge request gitlab-org/gitlab!82166

ProjectImport: Import remote file from AWS S3

See merge request gitlab-org/gitlab!77259

Remove non-human created tokens from PAT list

See merge request gitlab-org/gitlab!80716

Add an actor to FF check on work item type resolver

See merge request gitlab-org/gitlab!82154

Update Enterprise badge applies to SAML as well

See merge request gitlab-org/gitlab!82075

Send a notification when a new access token is created

See merge request gitlab-org/gitlab!81340

Changelog: added

Update error text

See merge request gitlab-org/gitlab!81926

Add HTTP status code to Jira connect client logs

See merge request gitlab-org/gitlab!81986

Switch to new GDK config for multiple databases

See merge request gitlab-org/gitlab!82267

Do not delete shared resource on live environments

See merge request gitlab-org/gitlab!82098

Remove ee uses of dev_env_or_com

See merge request gitlab-org/gitlab!82151

Remove null constraint from security_scan_succeeded column

See merge request gitlab-org/gitlab!81322

The old multiple_databases config is deprecated

Add audit event for project deploy tokens

See merge request gitlab-org/gitlab!81829

* Add an audit even when:
    * a new project deploy token is created.
    * a project deploy token is revoked via UI.
    * a project deploy token is deleted via API.

Changelog: added
EE: true

Remove personal_project_owner_with_owner_access feature flag

See merge request gitlab-org/gitlab!82088

This will make the fix generally available for owners of personal
projects to have OWNER access level membership.

Changelog: changed

Prevent object storage orphans when destroying project

See merge request gitlab-org/gitlab!81415

This commit prevents project from being destroyed
if any child objects with object storage are not
destroyed first.

chore: Clarify "Approvers" filter usage

See merge request gitlab-org/gitlab!81929

Add some wording to better distinguish "Approver" from "Approved-By"

Fix "Search for Code References" section is not properly located

See merge request gitlab-org/gitlab!82182

Add rule to enforce using clear instead of deselect

See merge request gitlab-org/gitlab!82058

Fix metadata tag for registry tests

See merge request gitlab-org/gitlab!79943

Removed obsolete HAML

See merge request gitlab-org/gitlab!80628

This removes some obsolete HAML:

* In app/views/ci/variables/_variable_row.html.haml, some code was
  guarded by a condition that always evaluates to false and has thus
  been removed.
* The app/views/shared/buttons/_project_feature_toggle.html.haml view
  has been deleted as it's not used anywhere anymore. From now on, we
  should use the Pajamas-complient _gl_toggle.html.haml view.

Related to: https://gitlab.com/gitlab-org/gitlab/-/issues/348874

Instead of using inheritance to share code among the project creation
classes, I refactor it to use composition. This away the code is a bit
more extensible and has more independent parts (less coupling).

`Import::GitlabProjects::CreateProjectFromRemoteFileService` and
`Import::GitlabProjects::CreateProjectFromUploadedFileService` was
replaced by a single entry point
`Import::GitlabProjects::CreateProjectService`.

`Import::GitlabProjects::CreateProjectService` is responsible to create
a project when the user parameters are valid. Since the user can use
different strategies to create/import a project, the requirements for
each strategy is implemented in different
`Import::GitlabProjects::Strategies::*` classes, this way the strategy
can be changed by dependency injection.

A `Import::GitlabProjects::Strategies::*` class must implement:
- initialize(current_user:, params:)
- valid? - validate the user parameters
- errors - when invalid, a ActiveModel::Errors object
- project_params - A hash with the specific strategy extra parameters to
  create the project

Also, because importing from a generic object storage and from AWS S3
have similar validations to be performed, the
`Import::GitlabProjects::Strategies::RemoteFileValidator` was created to
validate the remote file `content_length` and `content_type`.

MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/77259

Migrate IDE to use GlModal for discarding changes

See merge request gitlab-org/gitlab!81516

Disable clusters API if :certificate_based_clusters is disabled

See merge request gitlab-org/gitlab!81867

Docs: Correct feature flag link in upgrade page

See merge request gitlab-org/gitlab!82244