Migrate produ analytics view to internal events

Changelog: changed
EE: true

This commit removes the huge ee/spec/models/factories_spec.rb in favor
of linting factories per associated model.

Linting is run in a isolated, outer context starting with `Lint
factories for <described_class>`.

Add support for setting color and health status when creating a work item

Changelog: added

This MR removes the feature and documentation
for visual review tools.

Changelog: removed

- Embrace reusibility and DRYness by using shared examples in tests

Changelog: other

It's a scaffold for product usage activity tracking
for GitLab early access program. Only for participants
of the program and only who agreed on optional tracking.

Changelog: added

This change removes references when displaying a
runner in the project area, so it shows runner
manager fields.

It places the runner manager fields at the bottom
of the view.

Changelog: changed

- ensure test coverage for further refactorings during
  work on https://gitlab.com/gitlab-org/gitlab/-/issues/443674

Changelog: removed
EE: true

Changelog: removed
EE: true

- Rename `Gitlab::Pages::DeploymentUpdate` to `Gitlab::Pages::DeploymentValidations`
- Use `with_option` to avoid duplication
- Remove some rubocop Todos
- Refactor specs for clarity

Returns additional 'completions' endpoint information. This can be used
by clients to send requests directly to AI Gateway.

This task was deprecated since 16.6.

Changelog: removed

Co-authored-by: James Nutt <jnutt@gitlab.com>

Migrate cycle views event to internal events

In Rake, `namespace` blocks are eagerly loaded so RuboCop needs to flag
the use of `require` as well.

As part of the migration of legacy data types to SSF
we deprecated the legacy replication details routes
and added redirect for the following routes:

- /admin/geo/replication/designs
- /admin/geo/replication/projects

Changelog: removed
EE: true

The confidence field was deprecated in 15.4. These changes
remove the field completely.

Changelog: removed
EE: true

This MR is to followup with the cleanup of renaming
CreateEmptyEmbeddingsRecordsWorker to
CreateEmbeddingsRecordsWorker. We will be removing
the old worker and queue here.

Related to issue: https://gitlab.com/gitlab-org/gitlab/-/issues/441766

Changelog: deprecated
EE: true

Changelog: other

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

Changelog: changed
EE: true

This primarily affects MailDeliveryJob enqueues by ActionMailer.

Changelog: other

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

Changelog: changed

See https://docs.gitlab.com/ee/development/database/avoiding_downtime_in_migrations.html#swap-the-columns-release-n--1

Changelog: changed

This MR removes some existing style violations and the associated
`.rubocop-todo` entries.

We will be changing how catalog publishing works by moving
the metadata processing and publishing to release-cli.
In our ideal case, `Releases::CreateService` should not run
`Ci::Catalog::Resources::ReleaseService` and this should be in
a separate endpoint. And in the future, we'll also change the catalog
publishing service because we don't want to calculate the metadata
on the server side.

To this end, we are deferring the catalog publish decision to
release-cli;

- If release-cli sends `legacy_catalog_publish` true, then
`Releases::CreateService` publishes the catalog resource.
- Otherwise, it does not publish the catalog.
It only creates the release.

In this MR, we are adding the new `legacy_catalog_publish` parameter
to the `/releases` API endpoint. Then, we are using it in
`Releases::CreateService` to decide publishing the catalog resource.

We are also starting to send the `--catalog-publish` CLI option to
release-cli. This will notify the release-cli that "this release is a
catalog resource so send `legacy_catalog_publish` as true if you want
to publish this release". In the future, release-cli will still use this
flag but then it will not send the `legacy_catalog_publish` parameter.
Instead, it will call the catalog resource endpoint separately.

These changes are behind the FF `ci_release_cli_catalog_publish_option`.
We'll use this FF to control this change to prevent breaking changes.

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

Changelog: removed

Changelog: other
EE: true

Changelog: other

This is the first step to convert pipeline_id related to bigint for:
- merge_requests.head_pipeline_id

See https://docs.gitlab.com/ee/development/database/avoiding_downtime_in_migrations.html#initialize-the-conversion-and-start-migrating-existing-data-release-n

Changelog: added

In case of `have_gitlab_http_status(-1)` we've seen an
`RuboCop::Runner::InfiniteCorrectionLoop` error after upgrading RuboCop.

This commits side-steps this problem by checking if replacement is not
identical to the previous source version.

This reverts merge request !148160