This commit update `gitlab-secret_detection` gem with some minor changes
to work nicely for the changes introduced in other commits in this merge
request.

- Introduce Interfaces for Push Check to invoke Secret Detection
- Add Gitleaks Ruleset file consisting rules for scanning SD
- Add tests to confirm Secret Detection behaviour

https://gitlab.com/gitlab-org/gitlab/-/issues/432368

This moves two spec helpers into `gitlab-rspec`.

Running external methods can allocate I/O bound resources
(like PostgreSQL connection or Gitaly). This is forbidden when running
within a concurrent Ruby thread, for example `async` HTTP requests
provided by the `gitlab-http` gem.

Changelog: other

Changelog: added

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/135760
introduced a new gitlab-backup-cli gem, but it executed `git`, which
is not present in Cloud Native GitLab.

Fix this by avoiding `git` and fixing the Rubocop rules to inherit
from the parent gems config.

Changelog: changed

This change does not require semver_dialects, it was updated
in order to unblock access to newer thor versions.

When using the `gitlab-http` gem, you can pass the `async: true` option
and get a `Concurrent::Promise` object. Since there is no business
logic and external connection inside the async calls, it is thread-safe.

- move the check to the left a bit and allow developer
  to detect the issue quicker before danger.

Unite RSpec/InvalidFeatureCategory and RSpec/MissingFeatureCategory into
RSpec/FeatureCategory.

This not only reduces the amount of code but also side-steps potential
confusion with RuboCop rule Gemfile/MissingFeatureCategory.

When the default value is false the schema validation
is reporting a wrong inconsistency.

Changelog: fixed
Relates to: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133322

It exclude indexes that were created by constraints
from schema validations gem

Changelog: fixed

- Move the existing HTTP lib to LegacyHTTP
- Use the existing HTTP file to switch between HTTP and LegacyHTTP
via the new feature flag use_gitlab_http_v2
- Adjust test files according to the new changes

These changes are behind the feature flag use_gitlab_http_v2

Signed-off-by: Rémy Coutable <remy@rymai.me>

Optimistic locking is overriding the query_constraints method
and our patch was overriding it instead of overriding the
original method and the locking_version attribute was
lost during the update

Changelog: fixed

Use Tempfile.create instead of Tempfile.open

In order to support running of migrations in milestone order, this
commit adds some of the necessary classes and tests to make this work.

- Monkeypatch on ActiveRecord::Base

For an easy migration, in this step we are replacing all
UrlBlocker::BlockedUrlError exceptions with
HTTP_V2::UrlBlocker::BlockedUrlError

- Adding the gem to the Gemfile
- Initializing it and require its dependencies
- Removing the old patches

This change implements periodical sync worker for events data.

- Copy the contents and requirements of lib/gitlab/http.rb into
the new gitlab-http gem.
- While lib/gitlab/http.rb is using Gitlab::HTTP, the gitlab-http gem
is using Gitlab::Http. So, we can gradually migrate to the gem.

1. Use the database when running this specs
2. Add a RSpec context

- STDOUT by default, but a logger and log proc
 can be specified via configuration
- Add structured log configuration for logging
 dev/test

Also add specs for formatter

The `to_h` will return a hash with the following fields:
- type
- object_type
- table_name
- object_name
- structure_sql_statement
- database_statement

Relates to: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/129822
Changelog: added

This change allows redacting placeholders from raw SQL statements for
the ClickHouse database.

This change enables request and response compression for the ClickHouse
client.

Signed-off-by: Rémy Coutable <remy@rymai.me>