Make deploy_boards doc clearer about its requirements

See merge request gitlab-org/gitlab-ce!29682

Update Grafana and GitLab Monitor in component list

See merge request gitlab-org/gitlab-ce!29537

This commit checks off two of the three components in the table that we
added for the CEO Challenge in Contribute 2019:

* Grafana:
  https://gitlab.com/gitlab-org/omnibus-gitlab/merge_requests/3272

* GitLab Monitor:
  https://gitlab.com/charts/gitlab/merge_requests/787

Update docs on how to run E2E tests

See merge request gitlab-org/gitlab-ce!29823

Add Gitaly data to the usage ping

See merge request gitlab-org/gitlab-ce!29893

Add documentation on epic add/remove child relations quick actions

See merge request gitlab-org/gitlab-ce!29860

Use next_instance_of instead of any_instance_of

See merge request gitlab-org/gitlab-ce!29905

Backport changes made by EE to various YAML configuration files

See merge request gitlab-org/gitlab-ce!29606

For prepended classes, we need to use `expect_next_instance_of`
instead of RSpecs `any_instance_of` variants.

Errors in application settings panel shows wrong panel

See merge request gitlab-org/gitlab-ce!25434

Fixed failing GraphQL file import

Closes #63527

See merge request gitlab-org/gitlab-ce!29900

Improve bug severity definitions and consolidate guidance for clarity

See merge request gitlab-org/gitlab-ce!29694

Add embedding support to metrics_dashboard

See merge request gitlab-org/gitlab-ce!29696

This commits adds support for metrics dashboards
for embedding. If the flag 'embedded' is provided
to the environments/id/metrics_dashboard endpoint,
the response will be suitable for embedding in
issues or other content.

This is a precursor for support for embedding
metrics in GFM.

Gitaly data wasn't available to the team, an this change is a first
iteration towards understanding what data we need and how to interpret
it. Later more values will be added.

For now the most important thing is the filesystem String Array, as that
includes data on ext4 exposure and NFS.

Part of: https://gitlab.com/gitlab-org/gitlab-ce/issues/60602

Render last commit widget with Vue

Closes #62766

See merge request gitlab-org/gitlab-ce!29419

To make this happen, we need to conditionally add the group_saml
strategy when running tests, but only on EE. This requires some changes
to Gitlab.ee? so that it can be used before/without loading the Rails
environment. We also have to change how we require a few files, so this
can run outside of Rails.

Gitlab::JsonCache#parse_value ensure string

Closes #63510

See merge request gitlab-org/gitlab-ce!29885

Master i18n

See merge request gitlab-org/gitlab-ce!29801

[skip ci]

Docs: Link issue statistics api endpoint in the docs

See merge request gitlab-org/gitlab-ce!29855

Update Docs for Container Registry API Delete Endpoints

See merge request gitlab-org/gitlab-ce!29709

Add version text and edit section

See merge request gitlab-org/gitlab-ce!29875

Edit new Zoom call link content

See merge request gitlab-org/gitlab-ce!29878

Rename graphql files to match frontend docs

See merge request gitlab-org/gitlab-ce!29856

Adds the missing link to issues_statistics api endpoint

Documentation update for registry restore troubleshooting

Closes #63163

See merge request gitlab-org/gitlab-ce!29819

Restoring the registry ends up using the wrong file permissions,
breaking the registry.

Document the workaround while we look at improvements.

Remove import columns from projects table

See merge request gitlab-org/gitlab-ce!29863

Render markdown in GraphQL

See merge request gitlab-org/gitlab-ce!29700

This adds a `markdown_field` to our types.

Using this helper will render a model's markdown field using the
existing `MarkupHelper` with the context of the GraphQL query
available to the helper.

Having the context available to the helper is needed for redacting
links to resources that the current user is not allowed to see.

Because rendering the HTML can cause queries, the complexity of a
these fields is raised by 5 above the default.

The markdown field helper can be used as follows:

      ```
      markdown_field :note_html, null: false
      ```

This would generate a field that will render the markdown field `note`
of the model. This could be overridden by adding the `method:`
argument. Passing a symbol for the method name:

      ```
      markdown_field :body_html, null: false, method: :note
      ```

It will have this description by default:

> The GitLab Flavored Markdown rendering of `note`

This could be overridden by passing a `description:` argument.

The type of a `markdown_field` is always `GraphQL::STRING_TYPE`.