The main purpose of this is to migrate pages to object storage

Add 5-minute-production-app CI template

See merge request gitlab-org/gitlab!49487

Signed-off-by: Dmytro Zaporozhets <dzaporozhets@gitlab.com>

Board refactor - Decouple boardsStore from GraphQL boards [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!49783

Duplicate components to help decouple boardsStore

Update parallel matrix job

See merge request gitlab-org/gitlab!50342

Add clarification to colons in scripts

See merge request gitlab-org/gitlab!50360

Update integration testing docs with request specs preferred

See merge request gitlab-org/gitlab!50065

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

Instrument viewing merge request diffs file by file

See merge request gitlab-org/gitlab!48470

Handle git errors when cleaning up MR refs

See merge request gitlab-org/gitlab!50250

Access `resolved_on_default_branch` via attribute reader

See merge request gitlab-org/gitlab!50381

Gitlab::Git::Repository::GitError and Gitlab::Git::CommandError
errors can get raised when trying to cleanup MR refs. This will
result to the worker being retried and move to dead queue when
failed after the retry limit.

We don't need to retry in this case as the job will be scheduled
again when picked up by `ScheduleMergeRequestCleanupRefsWorker`
that runs every minute via sidekiq cron.

In order to understand how are users are using the view file by
file feature, we need to track:
- How many users viewed MRs file by file
- How many MRs are being viewed file by file
- How many MRs are being viewed

This is tracked on each request to `diffs_batch.json` since that's
when we show the file by file controls.

Strengthen NFS warnings

See merge request gitlab-org/gitlab!49842

Strengthen NFS warnings across reference architectures, and clearly indicate that it will still work, just will not be supported.

Update GitLab Runner Helm Chart to 0.24.0/13.7.0

See merge request gitlab-org/gitlab!50377

Resolve "Roadmap timeline header text color bug in dark mode"

See merge request gitlab-org/gitlab!50357

Bump rspec and friends gem dependencies

See merge request gitlab-org/gitlab!50349

Add E2E to test copying snippet file contents

See merge request gitlab-org/gitlab!49542

See https://gitlab.com/gitlab-org/quality/testcases/-/issues/1099

Namespace settings don't always exist for a group

See merge request gitlab-org/gitlab!50353

Enhance AutoFix Indicator on Vulnerability Report Page

See merge request gitlab-org/gitlab!49479

This commit enhances the Vulnerability Report
Autofix Indicator, it adds Merge Requests
and CI-Status to this Indicator.

Allow disabling of new sign ups for tunnel admin user

See merge request gitlab-org/gitlab!50035

Un-quarantine add delete email audit log e2e spec

See merge request gitlab-org/gitlab!50359

Improve badges UI text

See merge request gitlab-org/gitlab!50351

Add GraphQL mutation for adding oncall rotation

See merge request gitlab-org/gitlab!49206

Fix parsers design flaw

See merge request gitlab-org/gitlab!50223

Clone epic data when cloning issues

See merge request gitlab-org/gitlab!50097

Revise Protect documentation

See merge request gitlab-org/gitlab!49253

Moving Container Security docs and adding steps
that explain how to set up Container Security.

We don't need to pass the `report_data` and `report` objects around the
method as they are now attributes of the parser instance.

Previously we were instantiating the parser objects without passing any
initialization arguments. Because of this, we were passing the report
and the JSON text to the parse method and all the other utility methods
which was causing inflation on method signatures.

By just passing the report and the JSON text as the initialization args
to the instances, we can avoid passing them in between utility methods.