Add aud to JWT.
Change iss format to include protocol
Change sub from job_id to a string that contains project:ref_type:ref
Update spec to validate iss, sub, and aud changes.
Add alpha tag to Predefined Variables documentation.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/72555

Changelog: other

Gitlab::Database::Connection was a kitchen sink type of class: it had
methods for obtaining database information (e.g. the database name),
running WAL related queries, querying the status of transactions, and
more.

This commit splits this class into separate types. For example,
reflection related methods are now located in
Gitlab::Database::Reflection. Transaction related methods are moved into
the Transactions module. The method to get a WAL diff has been moved
into the LoadBalancer class.

With this also changes the use of these methods. For example, instead of
this:

    Gitlab::Database.main.cached_column_exists?(:users, :id)

You now write this:

    Users.database.cached_column_exists?(:id)

Apart from being shorter in many cases, it also decouples the code using
these methods from the main database. This makes it easier to support
multiple databases over time.

Add tests for LicenseManagementJobs metric.
Disable license_scanning_jobs tests.
Becaue the metric is temporary disabled we would need to
disable related tests as well.

This method adds getter/setter methods for the "cancelable" feature that
gets included in the job request payload from runner.

runner_features is an ambiguous name and we want to replace it with
runtime_runner_features. This commit adds the runtime_runner_features
and removes the delegate code and tests for runner_features.

Changelog: added

This commit cleans up the feature flag.

Changelog: performance

Changelog: added

- Use Variables builder to build scoped_variables.
- Migrate predefined_variables to builder

Changed: performance

This adds support for using the database load balancer with multiple
databases. Load balancing is applied to two classes:

- ActiveRecord::Base
- Ci::CiDatabaseRecord

Each class has its own load balancer, configuration, service discovery,
etc. Load balancing for the CI class is only enabled when a CI
configuration exists, as it can reuse the main load balancer when
there's no dedicated CI database.

Sticking technically supports multiple databases, but in practise we
apply the same sticking rules to all databases. This is due to how
LoadBalancing::Session is used: there is only one instance per
request/Sidekiq job, and it's not aware of what database connections did
what. This means that a write to database A will result in GitLab
sticking to the primaries of _all_ databases. The choice for this is
simple: it requires fewer code changes, and allows us to introduce
multiple database support in smaller increments.

One change we made to sticking is to turn the Sticking module into a
class, and attach an instance to every base module that has its own load
balancer. This makes it easier to apply sticking on a per-database level
in the future, without having to type
`Gitlab::Database::LoadBalancing::Sticking...` every time.

Sticking also supports reading and writing of data using the old Redis
key names. This ensures sticking continues to work during a deployment,
as during this window we'll run two different versions in production.
Once the code has been deployed to GitLab.com and has been confirmed to
work, we'll remove support for reading/writing the old keys.

Sidekiq also supports load balancing multiple databases. If a load
balancer/database doesn't have any WAL data in the Sidekiq job, we treat
the database as being in sync. This way we can support Sidekiq jobs
using both the old and new load balancing data.

See https://gitlab.com/gitlab-org/gitlab/-/issues/331776 for more
details.

Changelog: added

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70743

Changelog: other

Avoid 2PC when creating ci_builds

Add a column to ci_builds_metadata so each build can have access
to the list of features runner supports

Changelog: added

This change adds checks for 2PC offenses in the Ci:Build state machine
transitions.

Add CI_DEPENDENCY_PROXY_DIRECT_GROUP_IMAGE_PREFIX
predefined environment variable to projects.

Changelog: added

Introduce a table to store job trace metadata

Changelog: added

This method didn't actually need to join. `preload` is sufficient in
this case. This commit also introduces documentation for this specific
case in case others run into a similar problem in future.

Adds an Rspec tag that enables DB load balancing for the specified
context

Currently we are storing this in a class instance variable in
Gitlab::Database::LoadBalancing. This class is auto-loaded which
means it is also unloaded when a Ruby change is detected.

This moves this to a class instance variable in ActiveRecord::Base

Update specs to use project_features.container_registry_access_level
and to test public projects with a private container registry.

This module contained various methods that were forwarded to
Gitlab::Database::Connection. This commit removes these wrappers in
favour of using Gitlab::Database.main instead. This is done to make it
explicit what database connection should be used.

See https://gitlab.com/gitlab-org/gitlab/-/issues/331776 and
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/65262 for more
information.

Remove the application code that populates the ci_build_trace_sections
and ci_build_trace_section_names. This data is not read by the
application currently and we can save on space/maintaince and solve
problems with background migration for self-managed users by dropping
the table is subsequent MRs.
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/66674

This table was originally created to collect metrics on jobs but was
never used and an expiration policy of was never enforced.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/2505

There is the possibility that we will need to build out features that
need this data in the future, based on the future vision, but at this
time it is not being used, and we can re-add it while re-considering
the architecture at that time (likely in 2022).
https://gitlab.com/gitlab-org/gitlab/-/issues/32565

This feature flag prevents already-retried builds from being retried
again. This feature flag:

* shipped in GitLab 14.0:
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/62349

* enabled by defualt in GitLab 14.0:
  https://gitlab.com/gitlab-org/gitlab/-/merge_requests/63112

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

Changelog: changed

Changelog: changed

It's been around since 13.0. Wow.

Changelog: other

As in 13.0 we dropped support of license_management
artifact, now we can remove it from the codebase.

Issue https://gitlab.com/gitlab-org/gitlab/-/issues/299114

Changelog: removed
EE: true

Adds new reporter approval rule for code coverage.
Also renames the worker for syncing approval rules to a
more generic one because it is not security only anymore.

Changelog: added