Create a system note when manually created incident is closed

Align the ordering of partitioned tables

See merge request gitlab-org/gitlab!72697

Make `LoadBalancer` to re-use very similar connection

See merge request gitlab-org/gitlab!72698

Rails snippet: delete trial licenses

See merge request gitlab-org/gitlab!66467

Remove the dast_on_demand_scans_scheduler feature flag

See merge request gitlab-org/gitlab!72953

Upgrade sidekiq-cron gem

See merge request gitlab-org/gitlab!73093

Update Gitaly version

See merge request gitlab-org/gitlab!73168

Fix styling for Request CVE button in sidebar

See merge request gitlab-org/gitlab!72952

Docs: Repair list rendering in dev's test_guide

See merge request gitlab-org/gitlab!73162

Allow JOB-TOKEN to perform all release REST API operations

See merge request gitlab-org/gitlab!72448

The purpose of this feature is to allow Phase 3 of decomposition rollout
as described in https://gitlab.com/groups/gitlab-org/-/epics/6160#progress.

The idea is that we configure a separate DB (CI) with replicas, but due
to transaction visibility we need to share primary connection to `main`
database.

This adds a temporary feature enabled via `FF` to allow this type
of behavior change.

Before this change we would store `model` for the purpose of understanding
sticking context for a object. This changes to prefer `sticking` which
is directly connected to `LB` context on which the `sticking` is evaluated.

This is in preparation to allow asynchronous handling of replicas
and re-use of primary connection in a load balancing context.

Do not validate ProjectNamespaces for hierarchy

See merge request gitlab-org/gitlab!72758

Update feature categories

See merge request gitlab-org/gitlab!73059

In JiHu repository, there's an additional code to register this
table to be synchronized like:

    Gitlab::Database::Partitioning.register_models([
      Phone::VerificationCode
    ])

This does not present in GitLab repository, but only in JiHu repository,
and this will cause the table to move to the top of db/structure.sql along
with other synchronized partitioned tables.

This will align both repositories to be more consistent.

The same does also happen for FOSS where
incident_management_pending_alert_escalations and
incident_management_pending_issue_escalations are not aligned.

Update Gitaly version

See merge request gitlab-org/gitlab!73161

Add ability to pass in fields to new vulnerability list component

See merge request gitlab-org/gitlab!72765

Added support for actions level 2 in the widget extension

See merge request gitlab-org/gitlab!72770

Fix language for increasing/decreasing urgency

See merge request gitlab-org/gitlab!72845

Update Editor team endpoint custom thresholds

See merge request gitlab-org/gitlab!72681

Update label of select branch dropdown on chat integrations edit page

See merge request gitlab-org/gitlab!73098

Add release filter and title sort to issues page refactor

See merge request gitlab-org/gitlab!72894

Enable real-time issue assignees by default

See merge request gitlab-org/gitlab!71953

Set a low urgency for a selection
of the editor team endpoints as
per our new custom threshold guidelines.

Resolve "Update documentation type label references"

See merge request gitlab-org/gitlab!71375

Resolve "Required type label tooling changes"

See merge request gitlab-org/gitlab!71316

This uses the same actions component so that when
support for more actions gets added, the level 2
sections will also get this support added.

Closes https://gitlab.com/gitlab-org/gitlab/-/issues/341049

Edit UI text of the project Usage Quotas page

See merge request gitlab-org/gitlab!71985

This also mounts the Action Cable engine all the time.
Mounting the engine has minimal impact on memory so we should just mount
it all the time to reduce configuration complexity.

Changelog: added

Avoid removing PI approved label

See merge request gitlab-org/gitlab!72857

VSA: Move show outside private

See merge request gitlab-org/gitlab!73147