This ensures that job artifacts are destroyed in a consistent manner
regardless where the removal is initiated.

This refactors ServicePing::SubmitService to remove Service Ping payload
generation logic from it and let it have one responsibility - sending
the payload and handling the response from version-gitlab-com.

Since https://gitlab.com/gitlab-org/gitlab/-/merge_requests/85503,
payload generation is instead handled in GitlabServicePingWorker, where
it's then passed as an argument to SubmitService.

Relevant specs, docs and rake tasks are updated accordingly. Some specs
had to be removed in their entirety, since they tested generating the
payload rather than sending it.

We add "public: true" to all variables from the YAML config.
"public" is already "true" for variable items, so we don't need it.

- ease of code management

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357649
Changelog: changed

Changelog: added

This ensures that job artifacts are destroyed in a consistent manner
regardless where the removal is initiated.

The new service extracts parts of the existing Users::DestroyService and
Users::MigrateToGhostUserService. This will be used by a cron job doing
interruptible batched migration / deletion of users and associated
records with limited execution time.

Changelog: fixed

Count on pipeline/user scope, apply counter after commit, skip counter if no junit presented
Generate metric definition for junit report artifacts
Define event as option on metric definition
Update sidekiq worker definitions for Ci::TrackFailedBuildWorker
Use unified has_report? method on pipeline
Move clean_gitlab_redis_shared_state to the root level of spec
Test track_event calls
Make sure if the worker is being called after pipeline completion
Add rspec for multiple pipelines
Test complex scenario, when pipeline retried from failed fo success

We stringify the options hash so we should be checking the options using
a String key

Changelog: fixed

is now required

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

Changelog: fixed

- make part of product

Changelog: changed
EE: true

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

**Problem**

Project delete causes a timeout error, because of `DELETE FROM projects`
query.

**Solution**

Extract `merge_request_diffs` deletion process into a separate
statement.

Changelog: fixed

- scan release description for attachment links
- saves each of them to Gitlab
- rewrite release description with new attachment links

Details: https://gitlab.com/gitlab-org/gitlab/-/issues/15620

And use ::Packages::UpdatePackageFileService.

BREAKING CHANGE: existing Debian packages will be unreachable.

Changelog: changed

The extra field, error, is added to the log message
so that alerts can be easily generated when errors
occur while checking for spam.

The introduction of the protected branch caching via the
`hash_based_cache_for_protected_branches` feature flag could cause
tests to fail since the protected branch cache might have the wrong
values.

Normally the cache is refreshed since protected branches are created
with `ProtectedBranches::CreateService`, but in tests FactoryBot
creates them without the service. To ensure the cache is in a good
state in tests, mimic this cache clearing after the creation of a
protected branch in the factory.

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

There is no valid way to create an issue without a title and
the removed specs asserted precisely that.

The specs didn't fail before because the were not asserting that
the create operation was successful.

This commits is the first step toward dropping ci_builds.stage
column. We are now adding an association to a build a reading
through ci_stages to display build stage data.

In development and test environments, we raise an error when
YamlProcessor feature flag is called without a defined actor.

However, in unit tests of entries, we have to add `with_actor` to
each of them.

So, in this commit, we are restricting this requirement to
a spec helper. And for now, we are only calling it for
create_pipeline_service* specs to cover all pipeline creation domain.

It also removes remaining attention request support code.

Changelog: removed

- begin improving query count/latency
- improve performance and error budget

Changelog: performance
EE: true

Changelog: changed

* Contributes to https://gitlab.com/gitlab-org/gitlab/-/issues/366724
* Follow-up for: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92934

* Feature flag: https://gitlab.com/gitlab-org/gitlab/-/issues/370608

**Problem**

After testing new Protected branch cache with `dry_run: true` option, we
can start relying on it.

**Solution**

* Add feature flag to control `dry_run` status

* New CloudSQL routes for provisioning database
  instances and form submission
* Forms for provisioning Postgres, MySQL and
  SQL Server database instances
* Create instance form submission end-point that
  invokes related services
* Specs for frontend and backend changes
* I18n
* Link to FF rollout issue

This removes the `async_after_approval` feature flag and keep the
new code.

Old code on ApprovalService has been removed as well since they
won't be used anymore.

Changelog: changed

The spamcheck service has been updated with a new
model to detect spam in snippets. This MR updates
the Snippet create/update functionality to check
for spam using the newly available gRPC endpoint in
spamcheck.

Changelog: added

This addresses the deprecation issues introduced via
https://github.com/redis/redis-rb/pull/1059 and
https://github.com/redis/redis-rb/pull/1061.

Changelog: fixed

This reverts merge request !94778

Along with existing Redis reporting. Currently behind FF