Default enable new_pipeline_form

See merge request gitlab-org/gitlab!46915

Default enable the flag
new_pipeline_form.

Add cleanup status field to graphQL ContainerRepositoryType

See merge request gitlab-org/gitlab!47544

Remove DOMContentLoaded Eventlisteners

See merge request gitlab-org/gitlab!47790

Add "Promote to epic" issue actions dropdown item

See merge request gitlab-org/gitlab!47306

Reverse condition in GraphQL feature flag docs

See merge request gitlab-org/gitlab!47838

Add custom scanner filter to security dashboard

See merge request gitlab-org/gitlab!46540

Fix scoped labels color regression in dark mode

See merge request gitlab-org/gitlab!47602

Replace fa-chevron-down in project level VSA

See merge request gitlab-org/gitlab!47885

Replace fa-exclamation-triangle in markdown field

See merge request gitlab-org/gitlab!47786

This field is mapped on to an appropriate Enum graphQL type

Fix webpack configuration for Gitpod GDK

See merge request gitlab-org/gitlab!47199

Add new "Promote to epic" button for issues so that
users can more easily promote an issue to an epic.
Currently, a user can only promote an issue through
the /promote quick action.

Merge branch '229695-migrate-deprecatedmodal2-to-glmodal-in-ee-app-assets-javascripts-vue_shared' into 'master'

Refactor delete_confirmation_modal.vue to use GlModal

See merge request gitlab-org/gitlab!46149

This refactor the license delete confirmation modal
to migrate to GlModal and GlSprintf

Add started_at/completed_at timestamps to Elasticsearch migrations

See merge request gitlab-org/gitlab!47751

Remove safe navigation operator from Vulnerability description

See merge request gitlab-org/gitlab!47768

Enable iteration charts feature flag by default

See merge request gitlab-org/gitlab!45492

Also mention and link in the iteration docs page

Update GitLab Shell to v13.13.0

See merge request gitlab-org/gitlab!47875

https://gitlab.com/gitlab-org/gitlab-shell/-/merge_requests/433

Make messages for reaching storage limit clearer

See merge request gitlab-org/gitlab!47498

Some messages shown in the terminal were phrased unclear on how to
reduce storage capacity. This change will make those messages clearer.

New blackbox elasticsearch approach

See merge request gitlab-org/gitlab!39130

Docs: Changed Go Proxy example to plaintext

See merge request gitlab-org/gitlab!47855

Update ElasticDeleteProjectWorker to not be dependent upon project join

See merge request gitlab-org/gitlab!47683

Update docs script image

See merge request gitlab-org/gitlab!47869

Remove DOMContentLoaded Eventlistener

See merge request gitlab-org/gitlab!47653

Remove sync_metrics_dashboard feature flag

See merge request gitlab-org/gitlab!47704

When saving Elasticsearch migrations we set a started_at and
completed_at value. This will help us long term with debugging as this
information will make it much easier to find relevant logs for what
happened.

As this index was not declared with [strict dynamic
mapping](https://www.elastic.co/guide/en/elasticsearch/reference/7.x/dynamic.html)
it is totally safe to just add new fields to the payload without them
existing already in the configuration and I have tested locally that
this works as well.

For the sake of clarity, however, we have added them to the mappings as
there is no reason not to.