It was enabled by default since 16.7,
and we only try to migrate clickhouse databases
if they are configured.

Related to https://gitlab.com/gitlab-org/gitlab/-/issues/434848+

Changelog: added

This reverts merge request !144921

## What does this MR do and why?

Add and backfill project_id for cluster_agent_tokens.

This table has a
[desired sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-desired_sharding_key-for-automatically-backfilling-a-sharding_key)
configured ([view configuration](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/cluster_agent_tokens.yml)).

This merge request is the first step towards transforming the desired sharding key into a
[sharding key](https://docs.gitlab.com/ee/development/database/multiple_databases.html#defining-a-sharding-key-for-all-cell-local-tables).

This involves three changes:

- Adding a new column that will serve as the sharding key (along with the relevant index, foreign key and not null constraint).
- Populating the sharding key when new records are created, by adding a `belongs_to` association on the model with a `default` value.
- Scheduling a [batched background migration](https://docs.gitlab.com/ee/development/database/batched_background_migrations.html)
  to set the sharding key for existing records.

Once the background migration has completed, a second merge request will be created to finalize the background
migration and validate the not null constraint.

## How to verify

We have assigned a random backend engineer from ~"group::environments" to review these changes. Please review this merge
request from a ~backend perspective. The main thing we are looking to verify is that the added column and association
match the values specified by the [desired sharding key](https://gitlab.com/gitlab-org/gitlab/-/blob/master/db/docs/cluster_agent_tokens.yml)
configuration and that backfilling the column from this other table makes sense in the context of this feature.

When you are finished, please:

1. Trigger the [database testing pipeline](https://docs.gitlab.com/ee/development/database/database_migration_pipeline.html)
   as instructed by Danger.
1. Request a review from the ~backend maintainer and ~database reviewer suggested by Danger.

If you have any questions or concerns, reach out to @tigerwnz, @DylanGriffith or @manojmj.

This merge request was generated by a once off keep implemented in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/143774

This change was generated by
[gitlab-housekeeper](https://gitlab.com/gitlab-org/gitlab/-/tree/master/gems/gitlab-housekeeper)
using the Keeps::BackfillDesiredShardingKeySmallTable keep.

To provide feedback on your experience with `gitlab-housekeeper` please comment in
<https://gitlab.com/gitlab-org/gitlab/-/issues/442003>.

Changelog: other

- update createComponent method to be easier to use

Changelog: fixed

This commit will raise an error when detecting multiple
sequences owned by the same table. This will avoid weird situation
where the id was not generated correctly for some instances.

The version outdated information mentions the GitLab version
while in reality it looks for the KAS version.

Changelog: changed

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.

This was not working for 2 reasons:

1. The YML file URL was pointing to the HTML version and was not
   returning valid YML. It's been updated to the raw path now.
2. The YML from this URL contains more keys than just `version` and
   `date` so we needed to ignore those other keys when constructing our
   `Struct`

- I thought this was done via https://gitlab.com/gitlab-org/gitlab/-/merge_requests/145043
- Turns out, I forgot the `_` in the name of the ignored attribute and
  so it wasn't actually ignored. When I fixed the typo, the many
  instances where this setting was still referenced caused specs to fail.
  This MR fixes the typo and cleans up the reamining references.

Currently, events have indifferent access when being consumed but not
when being published. This caused a bug when trying to access event data
in a `store.subscribe if:` lambda.

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

* Add new component timezone form to profile_edit_form.

Use helpPagePath function to render Terraform Module
registry links for empty and non-empty state. This
affects both groups and projects.

Changelog: changed
MR:

Added task.id to respond the same as class defined `id`

- remove vm-method-spy violations
- remove vm-access violation

Count first 1000 deployments or return '999+'.

Changelog: added

As we migrated to MR Widget V2, the V1 files are no longer being used.
This commit removes all those files.

This commit creates the routing table for ci_stages.

Changelog: other

- This can cause issues as seen in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/142303#note_1781915037
  Where rails will start enumerating until that date hits.
  That makes it more likely to hit a merge conflict with other migrations.

Changelog: performance

We want to switch to the Deployment history tab if
there's nothing to show in Kubernetes overview.
Don't switch tabs when they were specified in the URL param.

Changelog: changed

Updates dynamic_field component to allow labelDescription prop

Reorders form inputs to group repository & wlif fields together

This commit introduces instrumentation for exclusive locks within the
modules `Gitlab::ExclusiveLeaseGuard` and
`Gitlab::ExclusiveLeaseHelpers`, enabling better monitoring and
visibility into lock usage.

When utilizing the `Gitlab::ExclusiveLeaseHelpers#in_lock` method, the
following metrics are now tracked:
- exclusive_lock_count`
- exclusive_lock_wait_duration_s
- exclusive_lock_hold_duration_s

Similarly, when using the
`Gitlab::ExclusiveLeaseHelpers#try_obtain_lease` method, the following
metrics are captured:
- exclusive_lock_count
- exclusive_lock_hold_duration_s

Notably, in the latter method, `exclusive_lock_wait_duration_s` is not
captured as the method returns immediately if the lease is already held,
thus no waiting time is incurred.

Fixing some specs as well.

Replaces the existing label GlDropdown used when creating custom
Value Stream Analytics with a GlCollapsibleListbox equivalent.

EE: true

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

**Problem**

There is no verification in `#finalize_fast_destroy` if the repository
exists. Because of that, `#delete_refs` can raise an unhandled exception
and block the project destroy process.

**Solution**

Handle `Gitlab::Git::Repository::NoRepository` exception.

Changelog: fixed

We are going to need to combine these apps into a single `new Vue` call,
so having them in the same file to start with will make things much
easier later on.

Signed-off-by: Andrew Smith <espadav8@gmail.com>

Remove use_registry_api_to_list_tags feature flag and
add notice re: availability of it in docs

Changelog: changed