GitHub Import documentation Vale fixes

See merge request gitlab-org/gitlab!69568

Update webpack on-demand compiler placeholder message

See merge request gitlab-org/gitlab!69570

Fix integer columns on new VSA table

See merge request gitlab-org/gitlab!69531

Remove bigint conversion triggers for events

See merge request gitlab-org/gitlab!69337

Use deep_dup in bulk update service

See merge request gitlab-org/gitlab!69138

Update doc to get list of  tags via rails console

See merge request gitlab-org/gitlab!69139

Added unapprove quick-action

See merge request gitlab-org/gitlab!69225

add the /unapprove quick action to MRs

Changelog: added
EE: true
Signed-off-by: Lucas Zampieri <lzampier@redhat.com>

Move CI job token details to new page in CI docs

See merge request gitlab-org/gitlab!69422

Allow to open table editing dropdown from headers

See merge request gitlab-org/gitlab!69499

Display correct action buttons when viewing non-text files

See merge request gitlab-org/gitlab!69286

A guide to planning a GitLab upgrade

See merge request gitlab-org/gitlab!64953

Externalize messages on EKS settings page

See merge request gitlab-org/gitlab!69125

Pipeline Graph: Improve recursive ancestoring

See merge request gitlab-org/gitlab!69408

Move usage_graph component to vue_shared folder

See merge request gitlab-org/gitlab!69374

Removes GitLab Pages legacy storage lease

See merge request gitlab-org/gitlab!69377

Remove Karma and anything related

See merge request gitlab-org/gitlab!68977

Display the table editing actions dropdown
in the table’s header as well. Do not allow
to insert rows before the table header

Changelog: changed

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