This change attempts to satisfy the following issue:

Follow-up from "Improve Direct Transfer logs"
<https://gitlab.com/gitlab-org/gitlab/-/issues/430880>

It allows us to associate a BulkImport::Logger instance with an
entity, creating a more user friendly API for consistent logging across
the Direct Transfer code.

Changelog: other

This commit updates the secrets push check to list and filter blobs:

* To be below a certain size threshold.
* If they have already been committed to the repository.
* If they are binary.

The Model Registry project setting can now be controlled via an API

Changelog: added
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/139004

- Utilize the Compare#generated_files method to set diff files as generated
- Add missing generated column for ContextCommit
- Add collapse_generated_diff_files feature flag

Changelog: added

Changelog: changed

Changelog: changed

This change adds functionality to publish
group of events to EventStore to reduce the number of
sidekiq jobs triggered for an event type.

Changelog: added

Allows pausing Sidekiq jobs when a ClickHouse migration is running

Adds a new API endpoint that receives events from GitLab Agent (KAS).
It will track events using internal event tracking.

Rename quick action /award to /react.

'/award' is still available as an aliased command.

Changelog: changed

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/433529

In the group and project member pages, the invite user modal is used to
query and filter users. When the top-level group has a SAML provider
enabled and the option `Enforce SSO-only authentication for web activity
for this group` only SAML users are returned.

Following https://gitlab.com/gitlab-org/gitlab/-/merge_requests/134570,
we replace the user API endpoint (`/api/v4/users.json`) for the new
group user API endpoint (`/api/v4/groups/[groupId]/users.json`) to get a
list users that have a SAML identity connected to the group, or service
accounts created by the group or subgroups

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

As the first step of the text interpolation implementation, this commit
adds TextInterpolator and TextTemplate classes. These classes are not
yet used - that will come in the next MR. Once text interpolation is
fully implemented and has been tested under a feature flag, the original
Interpolation and Template classes will be removed and these new classes
will be renamed.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/433002

Add field workItemStateCounts to project and group query

Changelog: added

This fixes an issue where connections may get checked out without
sending any data:
https://github.com/sidekiq-cron/sidekiq-cron/pull/438

Diff:
https://my.diffend.io/gems/sidekiq-cron/1.10.1/1.12.0

Changes:
https://github.com/sidekiq-cron/sidekiq-cron/blob/master/CHANGELOG.md

Changelog: changed

Changes the method to the correct encoding

Changelog: fixed

Updates GitHub Import to import `merged` events from GitHub

Changelog: added

Changelog: changed

When implementing new auto-cancel strategies, we realized that trigger
jobs don't accept `interruptible` and they have no effect on pipeline
auto-cancellation.

In this change, we are copying the `interruptible` keyword from builds
to triggers. Also, we are adding test cases for pipeline
auto-cancellation to show that trigger jobs do not affect
auto-cancellation.

Our main goal is that when we implement the "interruptible" auto-cancel
strategy, users can also set trigger jobs interruptible or not.

Changelog: added

Changelog: fixed

Changelog: changed

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

Changelog: fixed

Move /-/profile/active_sessions to /-/user_settings/active_sessions and
redirect end_point to new endpoint till next major release (17.0)

Changelog: changed

- Adds behavior to ide controller
  to auto create the OAuthApp if
  needed.
- See [original impl][1].

[1]: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/132496

Since the `ensure_batched_background_migration_is_finished` call should
correspond to the latest version of the schema we need to support for a
given batched background migration we can assume that we can lock the
spec to only run against that schema.

Now that we have introduced a `finalized_by` key in our
`db/docs/batched_background_migrations/*.yml' files we can use this to
automatically work out what schema to use running tests for a batched
background migration.

This work is also to support an effort to automatically finalize a
lot of batched background migrations which ultimately is holding up
https://gitlab.com/gitlab-org/gitlab/-/issues/429165. Saving us the
effort of setting `schema` in the spec will simplify this work.

This merge request also updates a specific spec
migrate_human_user_type_spec just so that we have an example to
demonstrate this works. This migration is already finalized in
`db/post_migrate/20230523101514_finalize_user_type_migration.rb` so we
add that version number to the `db/docs` file for this migration job.
Without locking the version in this spec it fails due to new required
columns not being set. This demonstrates the new functionality to
automatically select the schema version works.

This MR also moves some logic out of `spec_helper` and into
`spec/support/helpers/migrations_helpers` because it makes more sense
there.

Add a mutation to update the name of a branch rule.

Changelog: added

Changelog: added

Changelog: fixed

Changelog: changed

Adds the counts.service_desk_custom_email_enabled
metric to Service Ping. Provides the number of projects
that have Service Desk custom email enabled.

This is to ensure long running imports are not killed
AdvanceStage will now refresh jids upon job finishing

This MR also adds redis method expire to refresh timeout of jids

Changelog: performance

Organizations can facilitate the responsible disclosure of security
issues by providing public contact information. The standard way to do
this is by using a [security.txt](https://securitytxt.org/) file.

This MR introduces this feature by adding:

- a new application setting (text, max 2048 chars)
- updated admin UI to configure this instance-level setting
- updated application setting API to configure the setting
- a new controller to render the content when present
- updated documentation describing the feature and how to use it

When present, the content will be available at
`https://YOUR_INSTANCE/.well-known/security.txt`.
Authentication is not required to view this file.

Changelog: added

The MLflow Run artifact_url now support formats with and without a related model_version.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138715