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

Fix webpack configuration for Gitpod GDK

See merge request gitlab-org/gitlab!47199

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.

Add graphql Api for Snippet Replication

See merge request gitlab-org/gitlab!47448

GitHub and Jenkins only available at project-level

See merge request gitlab-org/gitlab!46583

Update vale and start using output template

See merge request gitlab-org/gitlab!47487

We can shrink the docker image if we don't need ruby

Follow up epics CSS page bundle - Fix Roadmap border in dark mode

See merge request gitlab-org/gitlab!47857

Update source installation to use Git from Gitaly

See merge request gitlab-org/gitlab!47613

Currently, there's quite a lot of different places which keep track
about which Git version is required by Gitaly in order to have it
operate correctly. This list is hard to keep current, and naturally
those places have diverged in the path.

To fix this, we're moving towards a single source of truth for the
current Git version, which is going to be Gitaly. To implement this,
Gitaly nowadays provides a "make git" target which automatically builds
a supported configuration of Git and installs it into the desired
location. While not yet done, the vision is that this allows us to
quickly iterate in case there are security vulnerabilities reported or
in case there's a bug in Git which impacts operations.

As a first target, this commit converts our source-based installation
instructions to use this target.

[GraphQL] Metrics: use Global-ID scalar

See merge request gitlab-org/gitlab!36100

Default `vue_issue_header` feature flag to on

See merge request gitlab-org/gitlab!47690

Default `vue_issue_header` feature flag to on to convert the
issue header actions to an ellipsis dropdown menu for
improved UX so the user can go to one spot for all issue actions.

Reject incomplete multibyte strings and other invalid UTF8

See merge request gitlab-org/gitlab!47658

Trying to encode the input to UTF8 before matching would cause errors
when the string includes incomplete multibyte characters or any
characters ruby can't convert to UTF8.