Add frontend validation to avoid duplicate asset link names

See merge request gitlab-org/gitlab!81591

Now we are showing a validation error when trying to create/edit
a release with duplicate asset link titles.

Changelog: changed

Fix security provider logo

See merge request gitlab-org/gitlab!82929

Add deployment approval comment field

See merge request gitlab-org/gitlab!82743

Migrate elastic search warning

See merge request gitlab-org/gitlab!82892

Reuse common logger implementation from gitlab-qa

See merge request gitlab-org/gitlab!82818

Change urgency of Ci::DropPipelineWorker to high

See merge request gitlab-org/gitlab!82927

CTRT edits to Labels documentation

See merge request gitlab-org/gitlab!79746

Part of TW FY23Q1 OKR

Remove closest_gitlab_subscription method in favor of root_ancestor

See merge request gitlab-org/gitlab!82840

Update SimpleCov

See merge request gitlab-org/gitlab!82836

A comment field allows users to describe why a deployment is approved or
rejected.

It shows a count of remaining characters. The count turns orange when 30
or less are left, and turns red once the comment is over the limit.

This counter should be added to GitLab UI (and made pajamas compliant),
but is good here for now.

Changelog: added
EE: true

Style more Markdown in email notifications

See merge request gitlab-org/gitlab!78604

Remove calls to deprecated `to_graphql`

See merge request gitlab-org/gitlab!82739

Use import svg logos as relative path is not working in production

Refactor environment scope to use constants

See merge request gitlab-org/gitlab!82847

On environments, only 2 scopes are valid: available and stopped. If an
invalid scope is passed via the query params, the controller attempted
to use it and would return a 500 error.

This behaviour is still useful for the JSON API, and so we only fetch
the environments if the format is JSON.

However, as the environments are fetched via API after the HTML is
returned, there's no need to query the environments when the format is
HTML, meaning no need to use the scope. This stops invalid query
params (like ?scope=foo) from returning a 500 error. To stop the
resultant API calls from failing, we can check to see if the requested
scope is valid. If it is not, default to the available scope.

Changelog: fixed

Fix sourcegraph breaking on project resolve endpoint

See merge request gitlab-org/gitlab!82447

- https://gitlab.com/gitlab-org/gitlab/-/issues/351058
- It does this by moving projects#resolve to its own
  controller.
- Now the ProjectsController can assume :namespace_id
  exists in the route.

Changelog: fixed

Experiment Clean up: change_continuous_onboarding_link_urls

See merge request gitlab-org/gitlab!80906

Update doc/development/documentation/index.md

See merge request gitlab-org/gitlab!81550

Remove block_project_serialization feature flag

See merge request gitlab-org/gitlab!82866

Update the docs to recommend GET

See merge request gitlab-org/gitlab!82913

Document Container, Cluster scanning required architecture

See merge request gitlab-org/gitlab!82862

Filter archived issues / MRs from GraphQL

See merge request gitlab-org/gitlab!82673

Fix test failure of spec/services/notification_service_spec.rb

See merge request gitlab-org/gitlab!82694

Update Gitaly version

See merge request gitlab-org/gitlab!82915

Update doc/development/documentation/index.md

See merge request gitlab-org/gitlab!81555

Update phrasing about users for Service Ping registration

See merge request gitlab-org/gitlab!82912

Expose iteration property for issues API

See merge request gitlab-org/gitlab!82813

Changelog: added
EE: true

Propose test for generic subheadings

See merge request gitlab-org/gitlab!82331