Stub DNS in the spec suite

See merge request gitlab-org/gitlab!22368

This implements stubbing throughout the spec suite for DNS queries,
of which there are many. It includes a few tweaks to continue to allow
resolution for local addresses. This solves an issue where non-standard
DNS setups prevent most of the spec suite from working locally, and
should also provide speed improvements to the CI pipeline on average
by removing a source of external requests.

Raise on failure by default in wait/retry in QA tests

Closes gitlab-qa#282

See merge request gitlab-org/gitlab!22864

Many cases of flaky tests have been caused by allowing the test
to continue even after a precondition isn't satisfied. This
change makes it harder for that to happen by raising an error
if the condition of a wait/retry block isn't met.

Improve test readability

See merge request gitlab-org/gitlab!23695

Apply darker color to headers and scan names

See merge request gitlab-org/gitlab!23104

Simplify Plan EE QA tests

See merge request gitlab-org/gitlab!23540

Upgrade bootstrap-vue

See merge request gitlab-org/gitlab!18913

Accept group path as ID when fetching notes from API

See merge request gitlab-org/gitlab!23535

Allow to pass group full path as ID when fetching epic notes
from API.

Exclude dummy CSRF controller from logs

Closes #198399

See merge request gitlab-org/gitlab!23693

Add suggestions with code blocks in Threads docs

See merge request gitlab-org/gitlab!23680

Fix for clone using deploy key spec

See merge request gitlab-org/gitlab!23090

- Add locator for Retry button in sidebar.vue
- Add retry! logic for a pipeline job
- Add remove variable logic for CI/CD
- Add CiVariable via API instead of UI in spec
- Make helper method private
- Leave test in quarantine to monitor result in nightly first
- Dequarantine after passing in nightly

Upgrade gitaly gem + integrate disk_statistics rpc

See merge request gitlab-org/gitlab!22226

Resolve "Add missing fields for Sentry error details GraphQL"

See merge request gitlab-org/gitlab!23483

- Refresh docs

Add WAF Anomalies controller and mock service

See merge request gitlab-org/gitlab!22736

Adds controller for serving anomaly request summaries for WAF. Serves
requests with polling interval of 5000ms and reactive caching

Part of the work to complete https://gitlab.com/gitlab-org/gitlab/issues/14707

Retry set_latest_merge_request_diff_ids!

See merge request gitlab-org/gitlab!23306

Setting up the ACE-to-Monaco transition related feature flags

Closes #198607

See merge request gitlab-org/gitlab!23666

Add CI variables to provide GitLab port and protocol

Closes #197665

See merge request gitlab-org/gitlab!23296

Show license badge for Gitlab.com member overview

See merge request gitlab-org/gitlab!23521

Refactor git controllers

See merge request gitlab-org/gitlab!23164

In https://gitlab.com/gitlab-org/gitlab/issues/39176
we're allowing resources other than projects to have
repositories attached.

Therefore, it doesn't make a lot of sense to have git
requests handled by controllers in the Projects
namespace.

This commit introduces the new namespace Repositories.

Refactor class assignment in ErrorTrackingListView

See merge request gitlab-org/gitlab!23653

Allow users to read broadcast messages via API

See merge request gitlab-org/gitlab!23298

Add changelog and add rspecs

Move Sidekiq worker weights to application code

See merge request gitlab-org/gitlab!23253

Track events for paid signup flow

See merge request gitlab-org/gitlab!23612

Buttons for Edit and Web IDE look like segmented control in file header

Closes #197500

See merge request gitlab-org/gitlab!23291

Add accidentally deleted project config for custom apply suggestions

See merge request gitlab-org/gitlab!23687

And make them private.

By moving these low-level methods to the bottom of the test file,
we improve the code readability.

Feature flag: removal of get_tag_messages_go

See merge request gitlab-org/gitlab!23607

Gitlab::RequestForgeryProtection::Controller#index is not actually
user-reachable; we use it as a way of testing whether a request contains
a valid CSRF token.

However, because we put a request through this controller, it gets
logged. That means we get confusing log entries for this controller and
API paths, which are duplicated - they have the same request ID as the
'actual' request.