Adds the ability to use project/group/instance CI
variables inside a .gitlab-ci.yml file include
block.

Changelog: added

Hide edit severity btn for users without permissions

See merge request gitlab-org/gitlab!66642

Work around a weird Rails constant loading behaviour

See merge request gitlab-org/gitlab!66667

Revised Package Registry settings text

See merge request gitlab-org/gitlab!66395

Convert old GraphQL types to newer type names (Part 7) [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!66563

Run minimal rspec jobs before merge request is approved

See merge request gitlab-org/gitlab!64903

Clean up feature_category for static analysis group

See merge request gitlab-org/gitlab!66661

in prep for interpreter

Connect Puma low-level error handler to Sentry in puma.rb example

See merge request gitlab-org/gitlab!66712

Optional is default data category

See merge request gitlab-org/gitlab!66613

Add gitlab repository attribute back

See merge request gitlab-org/gitlab!66605

Docs: Formatting tweak for a filename in a header

See merge request gitlab-org/gitlab!66690

Move ignore_column(s) from EE model to CE model

See merge request gitlab-org/gitlab!66738

Drop infrastructure for on-disk remotes [RUN ALL RSPEC]

See merge request gitlab-org/gitlab!66513

Update "rspec-parameterized" gem to v.0.5.0

See merge request gitlab-org/gitlab!66516

E2E: Test large github import

See merge request gitlab-org/gitlab!65563

Remove Duplication of Trial on Billing Page Subscription Header

See merge request gitlab-org/gitlab!66675

Add Ecosystem CPU-bound workers

See merge request gitlab-org/gitlab!66632

Add Auxiliary viewer specs for all file types

See merge request gitlab-org/gitlab!66718

To ensure the full rspec job is run on automated MRs,
there is a new rule `if-automated-merge-reqeust`
added in the rspec job rules prior to
the rule `if-merge-request-not-approved`.

The order of these two rules are important to ensure the job
is created in the pipeline, instead of `when: never` taking effect.

To ensure the minimal job is not run on automated MRs,
a reverse rule is added to the minimal job rules
using `if-automated-merge-request` with `when: never`.

Not having $CI_MERGE_REQUEST_APPROVED set may mean either:
- the merge request is not approved yet
- the pipeline is not a merge request pipeline

Edited code owners to make task-based

See merge request gitlab-org/gitlab!66296

Add warning to LS docs about runtime installs

See merge request gitlab-org/gitlab!66706

The new release of the gem allows referencing
"let" variables via 'ref' keyword in parameters.

Add warning to DS docs about runtime installs

See merge request gitlab-org/gitlab!66705

Adding in caveats for removing users

See merge request gitlab-org/gitlab!66777

Update User account page tier and version info

See merge request gitlab-org/gitlab!66647

Add error tracking client key

See merge request gitlab-org/gitlab!66466

Add vulnerabilities_allowed column

See merge request gitlab-org/gitlab!66673

into approval_project_rules table.

Changelog: added

To authenticate error tracking events in collector we need to make sure
request has the same public key as the one project has. Keys are safe to
to keep public because they only allow submission of new events.
We do not allow read access to any information for those keys.
So it should not be used anywhere else except error tracking collector.
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Changelog: added
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>