Add starboard_vulnerability endpoint

See merge request gitlab-org/gitlab!69022

Update GitLab User Doc for EKS supported version

See merge request gitlab-org/gitlab!69387

Extend PreventIndexCreation cop

See merge request gitlab-org/gitlab!69247

This commit extends our existing cop to catch false positives
when the table_name is a string or a constant.

Stop deploying to the legacy pages storage

See merge request gitlab-org/gitlab!69287

Fix Rubocop Graphql/Description offenses

See merge request gitlab-org/gitlab!69413

Prepare the database load balancer for always being enabled

See merge request gitlab-org/gitlab!68857

Correct the scope of the GitHub personal access token

See merge request gitlab-org/gitlab!69212

Merge branch '339502-address-require-string-literal-i18n-helpers-offenses-in-app-assets-javascripts-vue_shared' into 'master'

Fix require-string-literal-i18n-helpers error

See merge request gitlab-org/gitlab!69360

Add form to Admin Area to control Files API throttling

See merge request gitlab-org/gitlab!68560

Only report MysteryRedisDurationError for shared state Redis

See merge request gitlab-org/gitlab!69446

Growth experiment guide and rollout template update

See merge request gitlab-org/gitlab!69335

This commits prepares the database load balancing code for always being
enabled, even when no replicas are configured.

To achieve this, the load balancer now supports the "primary_only"
option. When enabled, the list of replicas is ignored (which is empty
anyway), and a fake replica is used instead. This fake replica simply
reuses the primary connection of the load balancer it belongs to. We
chose this approach as there's simply too much code that assumes at
least one replica is present when load balancing is enabled.

In addition, we make various changes to ConnectionProxy to allow us to
always enable the use of this class. As an example, some tests use code
like this:

    ActiveRecord::Schema.define do
      create_table :foo do
        ...
      end
    end

Internally Rails ends up performing some `respond_to?` checks to expose
certain methods (or not). Without defining a custom
`respond_to_missing?`, these checks return `false` and thus the method
isn't available.

We've also had to change a few more methods in the ConnectionProxy
object to handle forwarding trailing hashes. In the previous setup
certain tests would still trigger deprecation warnings. This can be
avoided by using `...` everywhere, and getting rid of the `sticky:`
keyword argument.

Changelog: changed

Backfill projects with CI coverage usage

See merge request gitlab-org/gitlab!69115

Document GitLab Pages splat and placeholder support in _redirects

See merge request gitlab-org/gitlab!59803

Update dependency prosemirror-markdown to ^1.5.2

See merge request gitlab-org/gitlab!69547

Refactor labels dropdown to GlDropdown

See merge request gitlab-org/gitlab!69263

Repurpose Gitaly SRE Subpage to GitLab AWS SRE Subpage

See merge request gitlab-org/gitlab!69250

Update dependency @gitlab/ui to v32.5.0

See merge request gitlab-org/gitlab!69381

Make sure we respect bundler config for Gemfile

See merge request gitlab-org/gitlab!69461

Spell out first use of DVCS in Jira docs

See merge request gitlab-org/gitlab!69534

Externalize page-title messages

See merge request gitlab-org/gitlab!69124

RuboCop: Ban more methods which might cause subtransactions

See merge request gitlab-org/gitlab!69315

Docs: improve code_review page

See merge request gitlab-org/gitlab!69334

Clarify use of resolvers in code

See merge request gitlab-org/gitlab!69458

Allow callsite in project for cross-database queries

See merge request gitlab-org/gitlab!69447

Add relationship between project and project namespace

See merge request gitlab-org/gitlab!68825

Fix a flaky time expectation and a flaky ordering-related expectation

See merge request gitlab-org/gitlab!69450

Starting from 14.3 we only allow zip-storage for pages.
So far we were deploying to legacy storage to allow users
to enable it in case of some problems appearing.

Now we finally removing support for legacy storage

Changelog: removed

Add milestone to license metrics

See merge request gitlab-org/gitlab!69398

Remove integrated_error_tracking feature flag

See merge request gitlab-org/gitlab!69303

Mark feature flags in Gitlab/MarkUsedFeatureFlags only once

See merge request gitlab-org/gitlab!69469