Fix up the docs warning detected by the vale Admin rule

See merge request gitlab-org/gitlab!70837

Correct the metadata for the Security Partners doc page

See merge request gitlab-org/gitlab!70725

Add feature flag note to group authorized agents docs

See merge request gitlab-org/gitlab!70762

Fix Vale issues for user/project/web_ide/index.md

See merge request gitlab-org/gitlab!70842

Upgrade gitlab-elasticsearch-indexer to v2.14.0

See merge request gitlab-org/gitlab!70442

Further edits to LDAP topic

See merge request gitlab-org/gitlab!70658

Add apollo to dependency proxy app

See merge request gitlab-org/gitlab!70800

Remove cutoff logic for expiration message

See merge request gitlab-org/gitlab!70584

Feat(Admin Subscriptions): Add future dated alert

See merge request gitlab-org/gitlab!69874

Update pending builds namespace traversal ids when needed

See merge request gitlab-org/gitlab!70691

Allow Geo node status updates during maintenance mode

See merge request gitlab-org/gitlab!70010

Docs: H1 tier info for instance-level clusters

See merge request gitlab-org/gitlab!70797

Docs: Nav steps match style guide

See merge request gitlab-org/gitlab!70804

Docs: Improve wording and use present tense

See merge request gitlab-org/gitlab!70805

Global Search - Header Search Autocomplete

See merge request gitlab-org/gitlab!70016

Rename DAST Sites services to use AppSec namespace

See merge request gitlab-org/gitlab!70768

Always enable the database load balancer

See merge request gitlab-org/gitlab!68042

Update Content Editor Packages

See merge request gitlab-org/gitlab!70765

Define request apdex counters instead

See merge request gitlab-org/gitlab!69154

Update the migration MR requirements

See merge request gitlab-org/gitlab!69768

Update Gitaly version

See merge request gitlab-org/gitlab!70807

Shrink the cross-database spec allowlist further

See merge request gitlab-org/gitlab!70776

Prevents child pipelines from rendering incorrectly on hover

See merge request gitlab-org/gitlab!70526

Remove unnecessary route

See merge request gitlab-org/gitlab!70277

The database load balancer would re-raise ConnectionNotEstablished
errors when encountering them. This can lead to user facing errors
whenever the application tries to connect to a new database that is not
(yet) online.

This was discovered while testing the changes for
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68042, after
adding a replica host that didn't exist.

Changelog: fixed

By always enabling the database load balancer we reduce the amount of
different code paths, make it easier for developers to interact with the
load balancing code (e.g. by adding metrics), and make it easier to add
support for multiple databases (e.g. by not having to check if the load
balancer is enabled or not).

As part of this commit we fixed various parts of the code that didn't
expect the load balancer to always be enabled (or at least when running
tests).

Changelog: added
Co-Authored-By: Dylan Griffith <dyl.griffith@gmail.com>

With this, we'll emit 2 new counters from web processes that can be
used to monitor apdex.

The `gitlab_sli:rails_request_apdex:total` counter is incremented for
every successful (not a 500) that is not to a health endpoint.

The `gitlab_sli:rails_request_apdex:success_total` is incremented when
the request took less than 1 second. We intend to customize this value
per endpoint in the future.

Both these counters are labelled with `feature_category` and
`endpoint_id` from the context.

The metrics would also be initialized on the first scrape. This means
that a 0 would be available for every set of labels, avoiding bugs in
calculations with these metrics.

To get to all of the `feature_category`s and `endpoint_id`s for the
initialization, we had to move some code that iterates all endpoints
that was only used in tests to the application.

We know this would initialize about 2 * 2500 metrics per pod
running a web server. So we'd like to roll this out in a controlled
fashion, to make sure this doesn't impact our monitoring. Which is why
this is feature flagged.

This also limits the initialization of these metrics to just
web-processes. So they don't get generated for consoles or runner
processes.

This also includes a developer-api to define SLIs and encourages
initializing them with the known label sets.