Add warning to stop Puma and Sidekiq when restoring from backup

See merge request gitlab-org/gitlab!40791

Create IssueLink for Vulnerabilities that do not have them, attempt 3

See merge request gitlab-org/gitlab!40726

As mentioned in https://gitlab.com/gitlab-org/gitlab/-/issues/224457 we
need to create missing `Vulnerabilities::IssueLink` objects for
Vulnerabilities that do not have them yet but have an associated
`Vulnerabilities::Feedback` with type of `issue`.

Drop http_default_timeouts feature flag

See merge request gitlab-org/gitlab!39188

Update Composer and PyPI docs with additional info

See merge request gitlab-org/gitlab!40617

Hide vendor name when GitLab is the only one

See merge request gitlab-org/gitlab!40370

Adds test cases controller and UI tab

See merge request gitlab-org/gitlab!40019

Optimize factory creation in user view issues spec

See merge request gitlab-org/gitlab!40447

Merge branch '225482-allow-reporters-to-run-jobs-that-deploy-to-an-environments-if-they-are-explicitly-listed' into 'master'

Deployer authorisation for protected environments

Closes #225482

See merge request gitlab-org/gitlab!38188

[RUN AS-IF-FOSS] Support custom Azure Blob Storage domains

See merge request gitlab-org/gitlab!40694

Migrate Bootstrap button to GlButton in boards modal

Closes #229345

See merge request gitlab-org/gitlab!40633

Fix date spec failure merge_request_analytics/graphql/throughput_chart_query_builder_spec.js

Closes #243437

See merge request gitlab-org/gitlab!40816

Fix throughput_chart_query_builder_spec.js
Due to we use current date as prototype, and manipulate month first to
get a date object, on 31st, when we move to a month with only 30 days,
the month will increase unintentionally.

Migrate application row bs-callout to glalert

Closes #242021

See merge request gitlab-org/gitlab!40756

Network policy editor preview

See merge request gitlab-org/gitlab!39407

Merge branch '240917-ensure-user-submits-trial-form-during-new-user-onboarding-signup-process' into 'master'

Skip onboarding issues exp. when in trial flow

See merge request gitlab-org/gitlab!40304

GitLab UI tooltips in HAML/Vanilla JS: Dispose tooltips

See merge request gitlab-org/gitlab!39379

Document auto language detection

See merge request gitlab-org/gitlab!40430

Quarantine cluster_with_prometheus test

See merge request gitlab-org/gitlab!40715

Geo Statuses - Fix empty section bug

See merge request gitlab-org/gitlab!40443

There was an issue when there was
NOTHING to show that it would
omit the progress bars.

This was not the desired behavior,
we instead want to show the queued
jobs.

Don't overwrite user's description by default template description

Closes #220941

See merge request gitlab-org/gitlab!40609

Add MergeRequestReviewer for dedicated Reviewers section

See merge request gitlab-org/gitlab!40358

It's added to prepare for dedicated reviewers section for MRs on EE

This commit implements yaml and humanized previews for policy editor

Add gitlab_subscriptions to the list of high traffic tables

See merge request gitlab-org/gitlab!40696

Add seats_in_use and seats_owed to gitlab_subscriptions

See merge request gitlab-org/gitlab!40470

Don't send SameSite=None to incompatible browsers

See merge request gitlab-org/gitlab!40667

The browser gem is quite inefficient for checking SameSite
compatibility. If we rewrite the checks, we see much better performance:

```
Warming up --------------------------------------
            no check    46.338k i/100ms
               check    21.325k i/100ms
Calculating -------------------------------------
            no check    446.012k (± 5.5%) i/s -      2.224M in   5.003135s
               check    210.757k (± 2.8%) i/s -      1.066M in   5.062987s

Comparison:
            no check:   446012.3 i/s
               check:   210756.9 i/s - 2.12x  (± 0.00) slower
```

We set `SameSite=None` in GitLab 12.10 via
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28205 because
Chrome v80, rolled out in March 2020, treats any cookies without the
`SameSite` directive set as though they are `SameSite=Lax`
(https://www.chromestatus.com/feature/5088147346030592). This is a
breaking change from the previous default behavior, which was to treat
those cookies as `SameSite=None`.

However, older browsers (e.g. MacOS 10.14 on Safari 13.0.3) may
interpret the `None` as `Strict`, which causes users that click on
gitlab.com links from third-party sites (e.g. Gmail, Slack) to log in
again.

https://www.chromium.org/updates/same-site/incompatible-clients
recommends a set of regular expressions to determine whether to send
this. This commit implements most of the logic but skips one case since
this doesn't seem common: macOS 10.14 with an embedded WebKit
browser. This is also what
https://rubygems.org/gems/rails_same_site_cookie does.

I considered using that gem
(https://gitlab.com/gitlab-org/gitlab/-/merge_requests/40663), but I
didn't like how it added another dependency (`user_agent_parser`) that
loads a large YAML database
(https://github.com/ua-parser/uap-ruby#the-pattern-database).

As we saw in https://gitlab.com/gitlab-org/gitlab/-/issues/36405, having
processes that can write to GitLab tables while restoring from a
database backup can cause duplicate rows be inserted and schema changes
to fail quietly. At the moment, we don't have a good story of restoring
a database backup in a single transaction, so we need to tell admins to
stop Puma and Sidekiq.