Most categories weren't used in the codebase except for
code_analytics.

In
https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/84649
code_analytics was merged into value_stream_management.

Geo: Replicate wiki and design HEAD ref if needed

See merge request gitlab-org/gitlab!68324

Revert "Merge branch 'mc-remove-column-from-project-settings' into 'master'"

See merge request gitlab-org/gitlab!68832

Fix Popover Trial Status Text for New Trials

See merge request gitlab-org/gitlab!68680

This reverts merge request !68798

Add jq snippet to sort activity by time across multiple logs

See merge request gitlab-org/gitlab!68655

Introduce CursorPager

See merge request gitlab-org/gitlab!68462

Fix bug validating EE project features

See merge request gitlab-org/gitlab!68523

Use GraphQL to delete a note

See merge request gitlab-org/gitlab!68757

Fixes suggestions with new line characters not working

See merge request gitlab-org/gitlab!68750

Remove column from project_settings

See merge request gitlab-org/gitlab!68798

Removes ci_same_stage_job_needs ff

See merge request gitlab-org/gitlab!68041

Introduce CursorPager service

Allow 'source' as an index parameter for pipelines if feature flag is enabled

See merge request gitlab-org/gitlab!68822

Ignore Ci::Build 2PC offenses with Deployment

See merge request gitlab-org/gitlab!68533

The current class `ProjectFeature` validates that none of the
project features have a value greater than `Featurable::ENABLED`,
except for the `pages` feature.

Nevertheless, we have an EE extension where we add more features to
the `ProjectFeature` class. The current validator use only the
constant `ProjectFeature::FEATURES` for the validation. This means
that the `ProjectFeature::EE_FEATURES` are not included in the
validation and we could set the `Featurable::PUBLIC` value.

In this commit we fix that by including all features set in the
`ProjectFeature` including both FOSS and EE ones.

Changelog: fixed

This was missed during a conflict-resolve for
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/67964.
Without this, pipeines can not be filtered by source from the UI.
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>

This change adds checks for 2PC offenses in the Ci:Build state machine
transitions.

Fix search depth in DS user documentation

See merge request gitlab-org/gitlab!68626

Enable assumeImmutableResults in DAST Site Profiles

See merge request gitlab-org/gitlab!68732

Improve epics resolver specs

See merge request gitlab-org/gitlab!68670

Removes participants and subscriptions from sidebar entity

See merge request gitlab-org/gitlab!68032

Remove feature flag milestone_reference_pattern

See merge request gitlab-org/gitlab!68358

Attempt to reduce flakiness ci/tags_spec array checks

See merge request gitlab-org/gitlab!68712

Set assumeImmutableResults to true in the Apollo provider
for DAST Site Profiles

Refer https://gitlab.com/groups/gitlab-org/-/epics/6025

These 2 values get retrieved through GraphQL so we don't need them.

Fix and improve compliance pipeline example

See merge request gitlab-org/gitlab!62775

Package build infos: remove safe_find_or_create_by! calls

See merge request gitlab-org/gitlab!68649

Add sentry_dsn to error tracking API

See merge request gitlab-org/gitlab!68767

Split "comment type" dropdown into a new component

See merge request gitlab-org/gitlab!68505

Remove cloud_license_enabled database column

See merge request gitlab-org/gitlab!65541

Add crosslinks to several permissions

See merge request gitlab-org/gitlab!68342

Split docs review apps in its own page

See merge request gitlab-org/gitlab!68347

Allow to reference board in ancestor group when creating epic

See merge request gitlab-org/gitlab!68039