Merge branch '34102-increase-cpu-request-for-gitlab-shell-and-workhorse-in-review-apps' into 'master'

Increase requested CPU for gitlab-shell, gitlab-workhorse and gitlab-runner

Closes #34102

See merge request gitlab-org/gitlab!18673

Document scenarios of different project pages

See merge request gitlab-org/gitlab!18499

Remove unneeded bullet point

See merge request gitlab-org/gitlab!18720

Enable frozen string for spec/graphql

See merge request gitlab-org/gitlab!18717

Partially addresses:

https://gitlab.com/gitlab-org/gitlab/issues/27703

Merge branch 'docs-make-it-easy-for-includes-to-add-jobs-at-beginning-end-of-pipeline' into 'master'

Add docs for .pre and .post pipeline stages

See merge request gitlab-org/gitlab!18664

Enable frozen string for spec/frontend

See merge request gitlab-org/gitlab!18705

Partially addresses:

https://gitlab.com/gitlab-org/gitlab/issues/27703

Added beta warning to documentation

See merge request gitlab-org/gitlab!18643

Highlight introduced version for instance-level environments

See merge request gitlab-org/gitlab!18714

Add E2E test of NPM registry

Closes gitlab-org/quality/testcases#220

See merge request gitlab-org/gitlab!18361

* Adds a docker service to publish an NPM package
* Adds QA selectors and page objects for the packages UI
* Adds `Runtime::Fixtures.with_fixtures` which allows fixtures to be
  created on-the-fly

Move scoped label spec to EE

See merge request gitlab-org/gitlab!18706

Independence for embed timewindow scroll

See merge request gitlab-org/gitlab!18109

Remove the pod_logs_reactive_cache feature flag

See merge request gitlab-org/gitlab!18574

Now that the frontend polls the pod logs API, we can enable reactive
caching for the API, which was behind the feature flag.

Allow maintainers to toggle write permission for public deploy keys

See merge request gitlab-org/gitlab!17210

Fix inability to set snippet visibility via API

Closes #34016

See merge request gitlab-org/gitlab!18612

Added Visual Review Bot

See merge request gitlab-org/gitlab!18663

Use Billing Plan Card layout in profile/billing and group/billing

Closes #13485 and #31471

See merge request gitlab-org/gitlab!15437

Transform billing plans table to cards from Bootstrap.

Minor fixes to new rake tasks content

See merge request gitlab-org/gitlab!18621

persist the refs when open the link of refs in a new tab of browser

Closes #30264

See merge request gitlab-org/gitlab!16636

Relevant to branch dropdowns in:
- Project view
- Code search

https://gitlab.com/gitlab-org/gitlab/issues/30264

Exclude people with no capacity from reviewer roulette

See merge request gitlab-org/gitlab!17119

JIRA Integration: Fix API URL with trailing slash

See merge request gitlab-org/gitlab!18526

JIRA URL works with trailing slash, this fixes the API URL.

Add AWS cluster provider

See merge request gitlab-org/gitlab!17057

Add individual inherited member lookup API

See merge request gitlab-org/gitlab!17744

Adds the endpoints

    /(groups|projects)/:id/members/all/:user_id

for finding individual members, including inherited membership,
complementing the existing endpoints

    /(groups|projects)/:id/members
    /(groups|projects)/:id/members/all
    /(groups|projects)/:id/members/:user_id

which list direct members, list all members (including inherited), and
find individual direct members, respectively.

Consider the scenario:

1. The snippet visibility level is set to internal
2. A user attempts to create a private snippet

Previously this would always fail because `default_value_for` would
overwrite the private visibility setting, no matter what
visibility_level was. This was happening because `default_value_for` was
confused by the default value of 0 specified by the database schema.

`default_value_for` attempts to assign the default value in the block by
checking whether the attribute has changed. The problem is that since
the default value by the database was 0, and the user requested 0, this
appeared as though no changes were made. As a result,
`default_value_for` would always overwrite the user's preference.

To fix this, we remove the use of `default_value_for` and only set the
visibility level to the default application setting when no preference
has been given at creation time.

This is similar to the fix in
https://gitlab.com/gitlab-org/gitlab-foss/merge_requests/29578.

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