This documents the use of /rebase for merge requests.

Also move rebase functionality into `MergeRequests::UpdateService` to
ensure merges/rebases are handled in the same location.

Since /rebase and /merge actions are not atomic, we may run into
confusing race conditions if these are applied together. For now, we
just ignore the /merge and proceed with the rebase.

This will make it easier for people to bring their merge requests
up-to-date.

Fix flaky spec in QuickActions::InterpretService#execute

See merge request gitlab-org/gitlab!50605

Remove FF ci_include_multiple_files_from_project

See merge request gitlab-org/gitlab!50577

Adds annotations to CiliumNetworkPolicies

See merge request gitlab-org/gitlab!50586

Set finding_uuid while creating feedback records

See merge request gitlab-org/gitlab!50495

Un-quarantine project export file download spec

See merge request gitlab-org/gitlab!50615

Improve details on queue_selector rename

See merge request gitlab-org/gitlab!50473

PgBouncer docs need to mention backups

See merge request gitlab-org/gitlab!50298

Remove duplicate tier info from RA docs

See merge request gitlab-org/gitlab!50578

Install the correct PostgreSQL version on Ubuntu 18

See merge request gitlab-org/gitlab!49817

Add note about toggle of Elastic Search pause

See merge request gitlab-org/gitlab!50355

Feature added via https://gitlab.com/gitlab-org/gitlab/-/merge_requests/34069 makes automatic changes to the
pause settings internally
which shows up on the UI too, even if a user did not directly perform
the change

Migrate runner_setup_controller_spec.rb to request spec

See merge request gitlab-org/gitlab!50600

Trial onboarding issues experiment

See merge request gitlab-org/gitlab!48052

Growth conversion experiment

Remove FF ci_bridge_dependency_variables

See merge request gitlab-org/gitlab!50596

The spec was attempting to test whether `/assign @userA @userB` would
only assign an issue or merge request to `userA`. However, this would
fail occasionally because the reference extractor does not guarantee
ordering with extracted Markdown references since a database lookup is
performed (e.g. `User.where`) without an ORDER BY.

We adapt the test to check that only one of the two possible users is
assigned since the behavior is ambiguous when multiple assignees is not
supported, and it would take some work with some performance
implications to ensure the first mentioned user were assigned.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/27989

Replace user controller spec with its request spec

See merge request gitlab-org/gitlab!50435

Revert occasionally increased timeout

See merge request gitlab-org/gitlab!50602

Upgrade @vue/test-utils to v1.1.2

See merge request gitlab-org/gitlab!50598

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Enable FF ci_rules_variables by default

See merge request gitlab-org/gitlab!50501

This includes sessionless shared examples for request spec copied
from the existing ones for controller spec.
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Improve service desk UI text

See merge request gitlab-org/gitlab!50407

Also made some documentaiton improvements

- make allowed deprecations list as small as possible

@vue/test-utils deprecated `attachToDocument` in 1.0.x

Regenerate outdated snapshots due to @vue/test-utils upgrade

It is already enabled by default.

Upgrading VTU to v1: Remove deprecated `setMethods` calls

See merge request gitlab-org/gitlab!50592

Add project scope to ci clint graphql endpoint

See merge request gitlab-org/gitlab!50418