Remove `options` assignment from ExtractsPath

See merge request gitlab-org/gitlab-ce!23389

Migration to write fullpath in all repository configs

Closes #41776

See merge request gitlab-org/gitlab-ce!22322

using_docker_images.md: document services inheriting dns and addn hosts settings

See merge request gitlab-org/gitlab-ce!23333

Add notice for web temrinal on GitLab.com

See merge request gitlab-org/gitlab-ce!23269

Always prefer flash-text as display block

Closes #53920

See merge request gitlab-org/gitlab-ce!23382

Update d3 to match the mermaid version

See merge request gitlab-org/gitlab-ce!23383

Or otherwise do not try to write repo config.

There is no need to make a difference between a Group or User
namespace, so also no need to define the classes of those.

And run in intervals.

In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16027 it was
added to write `gitlab.fullpath` in the git config of all
repositories. But this only writes them on move or migrate to hashed
storage.

This adds a migration that writes the fullpath to all the
repositories.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/41776

Lock writes to trace stream

Closes #51502

See merge request gitlab-org/gitlab-ce!23332

Correctly handle data-loss scenarios when encrypting columns

Closes #53763

See merge request gitlab-org/gitlab-ce!23306

If the EncryptColumns background migration runs in a sidekiq with a
stale view of the database schema, or when the purported destination
columns don't actually exist, data loss can result. Attempt to work
around these issues by reloading schema information before running
the migration, and raising errors if the model reports that any of its
source or destination columns are missing.

This assignment is only used by the Projects::NetworkController, so
we're needlessly assigning this very generically-named instance variable
on every controller which includes `ExtractsPath`, which is quite a few.

Further, the way we were passing this hash to
`HashWithIndifferentAccess` caused the following deprecation warning
after upgrading to Rails 5:

    DEPRECATION WARNING: #to_hash unexpectedly ignores parameter
    filtering, and will change to enforce it in Rails 5.1. Enable
    `raise_on_unfiltered_parameters` to respect parameter filtering,
    which is the default in new applications. For the existing
    deprecated behaviour, call #to_unsafe_h instead. (called from new at
    lib/extracts_path.rb:116)

Resolve "Jump to top in merge request"

Closes #52276

See merge request gitlab-org/gitlab-ce!23069

Suggest issues when typing title

Closes #22071

See merge request gitlab-org/gitlab-ce!22866

Fix top padding for new project form when error message is present

See merge request gitlab-org/gitlab-ce!23384

Resolve "Fix overlapping separator on the mobile navigation bar"

Closes #53874

See merge request gitlab-org/gitlab-ce!23126

Json logging for k8s Integration

See merge request gitlab-org/gitlab-ce!23328

Update GitHub integration docs to mainly follow GitHub updates.

Closes #53248

See merge request gitlab-org/gitlab-ce!22643

Replace deprecated skip-auto-migrations occurrence

Closes #45031

See merge request gitlab-org/gitlab-ce!23326

Add link to infra issue about Pages access control

Closes #54269

See merge request gitlab-org/gitlab-ce!23352

This suggests possibly related issues when the user types a title.

This uses GraphQL to allow the frontend to request the exact
data that is requires. We also get free caching through the Vue Apollo
plugin.

With this we can include the ability to import .graphql files in JS
and Vue files.
Also we now have the Vue test utils library to make testing
Vue components easier.

Closes #22071