We seem to be incurring significant egress bandwidth charges
transferring data from dev.gitlab.org, which is in Azure. Our CI runners
pull from the container registry on dev.gitlab.org, which then
communicates with Amazon S3. We should move our images back to
GitLab.com because:

1. Reliability: GitLab.com has a high-availability setup.
2. Cost: Network transfers within Google regions should be cheaper than
crossing cloud providers.

Document kind of tag that is created from the UI

See merge request gitlab-org/gitlab!18194

Resolve "Hide redundant labels in issue boards"

See merge request gitlab-org/gitlab!17937

Before in issue boards, a card showed labels including the list label.
The list label is redundant since you can see the list label at the top
of the card collection and adds noise. This commit removes list labels
from inside list label cards.

Merge branch '33750-follow-up-from-resolve-deactivate-a-user-with-self-service-reactivation' into 'master'

Do not allow deactivated users to use slash commands

See merge request gitlab-org/gitlab!18365

Remove execute permissions from PNG file

See merge request gitlab-org/gitlab!18417

Convert Burndown charts to gitlab-ui component

See merge request gitlab-org/gitlab!15463

We are using echarts for all charts

Split summary and alert details params

Closes #31883

See merge request gitlab-org/gitlab!18261

Extend Events lifetime to 3 years instead of 2

Closes #33840

See merge request gitlab-org/gitlab!18399

We eventually want to avoid deleting any Events, see
https://gitlab.com/gitlab-org/gitlab/issues/24538.

Resolve "Broken FOSS `master` due to `docs lint`"

Closes #33811

See merge request gitlab-org/gitlab!18402

Merge branch '30497-race-condition-in-discussions-json-request-could-lead-to-notes-showing-inconsistently-with-selected-notes-filter' into 'master'

Fix notes race condition when linking to specific note

See merge request gitlab-org/gitlab!17777

Before, notes (discussions.json) would be fetched twice in the following
case:
* User has a "Show comments only" or "Show history only" filter
* User then goes to an issue with a note hash, i.e. #note_*
* Frontend then makes two notes requests:
  1. Notes for the user's original filter
  2. Notes for "Show all activity" so that the note is definitely shown

This commit fixes this race condition so that there is always only
one note request made whether it is for a specific note or not.

Adding troubleshooting for invalid pin code

See merge request gitlab-org/gitlab!18078

API call to get a list of Project's Vulnerabilities

See merge request gitlab-org/gitlab!18269

Add "environment" dropdown to pod logs screen

See merge request gitlab-org/gitlab!17532

- Add dropdown to select environment in page
- Display logs of first pod found if no pod is selected
- Add environment_logs_data to display data required on the page
- Update specs

Merge branch '33758-nomethoderror-undefined-method-log_geo_deleted_event-in-objectstorage-backgroundmoveworker-job' into 'master'

Fix undefined method log_geo_deleted_event for MergeRequestDiff

Closes #33758

See merge request gitlab-org/gitlab!18405

Implement new query backend for Cycle Analytics

See merge request gitlab-org/gitlab!16775

- Providing median based on durations defined by the stage
- Providing list of serialized objects by stage
- Introduce DurationFilter class that decides whether we need
additional filtering to avoid negative durations

Add vendored template for Browser Performance Testing

See merge request gitlab-org/gitlab!17319