Merge branch '9957-move-ee-differences-for-app-assets-javascripts-monitoring-components-dashboard-vue-ce' into 'master'

Remove EE differences for monitoring dashboard

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

Fix jupyter rendering bug that ended in an infinite loop

Closes #59079

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

Removes EE differences for boards.scss

Closes gitlab-ee#10518

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

Docs review for MR 25586

Closes #59262

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

Update testing guide to reference test design

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

Allow external diffs to be used conditionally

Closes #54670

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

Update fugit which fixes a potential infinite loop

Closes #59273

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

Update gitlab-markup to 1.7.0 and document Python3 requirements

Closes #59062

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

Remove N+1 queries from users autocomplete

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

Fix Auto DevOps missing domain error handling

Closes #59546

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

Allow personal access token env var from gitlab-qa

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

gitlab-qa accepts an env var named GITLAB_QA_ACCESS_TOKEN, but here we
only accepted PERSONAL_ACCESS_TOKEN.

This change replaces PERSONAL_ACCESS_TOKEN with GITLAB_QA_ACCESS_TOKEN

Properly handle `ee` migration specs

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

[CE] Reduce diff with EE in `spec/policies`

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

For some reason this value can be an empty string and we want to ensure
that we correctly fail the job before a deploy. This is particularly
problematic at the moment when coupled with
https://gitlab.com/gitlab-org/gitlab-ce/issues/54760 as the user has no
easy way to recover without destroying the cluster and starting over.

Update U2F recommendations, fix #57656

Closes #57656

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

Rename build to job in webhooks docs

Closes #42254 and #28226

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

Revert "Merge branch '13784-validate-variables-for-masking' into 'master'"

Closes gitlab-ee#10740 and gitlab-ee#10738

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

This reverts merge request !25476

Upgraded Vue to 2.6.10 and also Vuex to 3.1.0

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

Upgrade to latest Version

Log Gitaly RPC duration to api_json.log and production_json.log

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

Add control for masking variable values in runner logs

Closes #13784

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

Add a masked switch to variable rows
Copy some behavior from the protected switch

Refactor verify_pages_domain_service specs

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

Add specs for new/disabled pages domain
Extract contexts from examples
Use `let` instead of `set` since domain is being changed
in each example

[QA] Toggle Gitaly N+1 detector via feature flag and run tests

Closes gitlab-qa#374

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

First attempt at allowing a feature flag to be set via the command line
when running tests. This will enable the flag, run the tests, and then
disable the flag.

Using OptionParser meant changing how scenarios get the instance
address, so this also allows the address to be set as a command line
option. It's backwards compatible (you can still provide the address
as the command line option after the scenario)

Update bootstrap to 4.3.1

Closes #52091

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

Expand and improve autofetch of endpoint section

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

Recommend disabling NFS server delegation

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

Prepares suggestion implementation for multi-line support

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

Externalize strings in controllers

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

- concerns
- dashboard
- groups
- import

Since external diffs are likely to be a bit slower than in-database
ones, add a mode that makes diffs external after they've been obsoleted
by events. This should strike a balance between performance and disk
space.

A background cron drives the majority of migrations, since diffs become
outdated through user actions.