Instead of creating environment and deployment on build creation add
this as a new prerequisite for builds. This way we are not going to
unnecessary create records (e.g. for builds with manual start).

Fix specs that assume environment and deployment will be created
immediately when build is created.

Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/27644.

Migrate managed clusters that aren't using managed features to unmanaged

Closes #62772

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

Migrate clusters with no token to unmanaged

Closes #62772

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

Omit issues links in merge request entity API response

Closes #63546

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

using_docker_images.md: fix config.json path

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

The merge request widget has a section that includes which issues may be
closed or mentioned based on the merge request description. The problem
is that rendering and redacting Markdown can be expensive, especially
since the browser polls for the data every 10 seconds.

Since these links don't change much and are just nice to have, we only
load them on first page load. The frontend will use the existing data if
the data doesn't appear on subsequent requests.

This saves about 30% of the rendering time of this endpoint, which adds
up to significant savings considering that
`MergeRequestsController#show.json` is called over a million times a day
on GitLab.com.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63546

Make deploy_boards doc clearer about its requirements

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

There are clusters that have Kubernetes namespaces
stored which are missing a service account token.
These namespaces are unable to be used for deployments,
so marking the clusters as unmanaged will allow the
platform credentials to be used instead.

Update Grafana and GitLab Monitor in component list

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