Previously the cloud native job log (aka CI live trace) Fog
implementation used the `put_object` and `delete_object` API
calls. These are object-storage specific API calls, and they work for
AWS and Google.

However, Fog has a more general API that works for all providers. We
already use this API for backups. To make live job logs work with Azure,
we use that general API.

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

Fixed some of the broken external links in GitLab documentation

See merge request gitlab-org/gitlab!46298

Update curl style requirements

See merge request gitlab-org/gitlab!45782

Add reliable tag to issue board e2e specs

See merge request gitlab-org/gitlab!46261

Usage quotas update storage tooltip content

See merge request gitlab-org/gitlab!45913

Add secret detection token revocation columns

See merge request gitlab-org/gitlab!45912

These columns will be used in conjunction with a revocation API

Quarantine project_templates_spec.rb Instance test

See merge request gitlab-org/gitlab!46169

Change Project Templates Spec Instance quarantine type from investigating to bug based on ticket information

Make experimentation subject index unique per experiment

See merge request gitlab-org/gitlab!45733

Before this change, we always bucketed the same users into the same
groups (control or experimental) for the same percentage rollout
regardless of the experiment key. After this change, the same user may
end up in the experimental group for one experiment and the control
group for a different experiment even at the same percentage rollout.

Docs: try out suggestion-level substitutions

See merge request gitlab-org/gitlab!28060

Our current substitutions file in Vale is set to the error level,
which is not appropriate for all of the suggestions we want to make
to the technical writing team. This commit adds another substition
file with a name that makes clear the items within it are at a
suggestion level, rather than an error level.

Add helpful details to fixture error message

See merge request gitlab-org/gitlab!45826

The database fixtures for development can fail when the database is
being re-created without having deleted the old repositories from
Gitaly. This expands the error message to provide a hint about how
to fix that.

Add github host to API and clients

See merge request gitlab-org/gitlab!45188

Docs: Recommend multi-stage builds for efficient Docker image builds

See merge request gitlab-org/gitlab!46032

Add end-of-life status to docs styleguide

See merge request gitlab-org/gitlab!46274

Update GitLab Kubernetes Agent Server version

See merge request gitlab-org/gitlab!46282

Docs: Edited Maven topic

See merge request gitlab-org/gitlab!46072

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

Fix empty icon for iteration system notes

See merge request gitlab-org/gitlab!45642

Clarify what happens during project repository storage moves

See merge request gitlab-org/gitlab!46083

Update Package docs to drive contributions

See merge request gitlab-org/gitlab!46287

Set defaults for cleanup policy regexes

See merge request gitlab-org/gitlab!44757

Fix filter comments e2e spec

See merge request gitlab-org/gitlab!45825

Adds checks to filter comments e2e spec and updates selectors

Add documentation for gitaly_ruby_json.log

See merge request gitlab-org/gitlab!46025

More realistic github import API example

See merge request gitlab-org/gitlab!46247