Historical vulnerability statistics supposed to be updated once a day
by a cronjob because updating them always for each update/insert of a
vulnerability can reduce the throughput of our worker classes and API
endpoints.

With this change, to be able to observe the side effects of disabling
the update logic of historical vulnerability statistics, we are moving
it behind a feature flag. We will remove the logic and the feature flag
eventually.

Changelog: other
EE: true

Fix Vale issues in ./administration/geo/replication/troubleshooting.md

See merge request gitlab-org/gitlab!67989

Update dependency proxy docs enabled by default

See merge request gitlab-org/gitlab!68090

Dequarantine Security Reports Spec tests

See merge request gitlab-org/gitlab!68071

Adds details about uploading license when no internet

See merge request gitlab-org/gitlab!68073

Dont cache root path in file_paths method

See merge request gitlab-org/gitlab!68081

Ensure service discovery runs before secondaries are used

See merge request gitlab-org/gitlab!67899

Document custom matchers for post-deployment migrations

See merge request gitlab-org/gitlab!67503

Updated nav steps to match standards

See merge request gitlab-org/gitlab!68116

Geo: Fixes to SSF guide for new blobs

See merge request gitlab-org/gitlab!68077

Update Auto DevOps' auto-deploy-image to v2.12.0

See merge request gitlab-org/gitlab!68103

Enable seat usage export (remove seat_usage feature flag)

See merge request gitlab-org/gitlab!67934

Added troubleshooting steps to snippet docs

See merge request gitlab-org/gitlab!67859

Add developers and maintainers to security policy project

See merge request gitlab-org/gitlab!67657

Remove dead code composer file system

See merge request gitlab-org/gitlab!67843

Merge branch '330682-update-deployments-hooksworker-to-utilize-new-sidekiq-readonly-database-replicas' into 'master'

Update Deployments::HooksWorker to use Sidekiq readonly DB replicas

See merge request gitlab-org/gitlab!67878

Fix vale and style issues in Service Ping docs - part 1

See merge request gitlab-org/gitlab!67612

Duing application init connection can be assigned to `NullPool`

See merge request gitlab-org/gitlab!68154

Refactor weight select in board scope

See merge request gitlab-org/gitlab!67928

Prevent mutating props and make selector more consistent with other
selectors
Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/67928/
EE: true

Enable ff_group_membership_export flag by default

See merge request gitlab-org/gitlab!68140

Add container registry migration eligibility flag to all tokens regardless of action [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!67852

Delete backups/tmp after restore

See merge request gitlab-org/gitlab!67741

GithubImporter: Ensure to fail and log imports on exceptions

See merge request gitlab-org/gitlab!67454

This appears to be a case for lazy init of performance bar
that in some circumstances results in a exception raised
as `db_config` is undefined

Integrations metrics dictionary

See merge request gitlab-org/gitlab!68137

Add db_config_name label to prometheus database metrics

See merge request gitlab-org/gitlab!67806

Add support for rendering subscript/superscript in content editor

See merge request gitlab-org/gitlab!68106

Add performance_indicator_type metric

See merge request gitlab-org/gitlab!68146

Currently, the Github Importer might end up stuck even after failing to
import the git repository. This might also happen when importing other
types of objects from Github.

To provide better feedback to the end user this kind of exception will
now mark the import (import_state) as failed. Also, to provide
information to developers and testers the exceptions errors will be
logged (importer.log) and saved in the import_failures table.

== What was done

* Created Gitlab::Import::ImportFailureService: This way we now have a
  standard way to log exceptions/errors that happens while importing a
  project;
  * All the exceptions/errors are logged to the importer.log with a
    standard format;
  * All the exceptions/errors are tracked in Gitlab::ErrorTracking;
  * All the exceptions/errors are recorded in the import_failures table;
  * When required, the exception/error might mark the whole import as
    failed;
  * This was created in a more generic way because it can later be used
    in the other importers (bitbucket, gitlab, etc);

* Updated Github Importer workers/importers to leverage of the
  Gitlab::Import::ImportFailureService;

* Updated Gitlab::GithubImport::Queue, to use
  Gitlab::Import::ImportFailureService when jobs exhausted retries;

* Updated Gitlab::Import::StuckImportJob to use
  Gitlab::Import::ImportFailureService;
  * This is also used in the Jira importer;

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

Changelog: fixed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/67454

Changelog: fixed

Resolve "Migrate RedisHLL metrics to instrumentation classes"

See merge request gitlab-org/gitlab!67820