Expose runbook in alert GraphQL API

See merge request gitlab-org/gitlab!38510

Add move note to ECS template details

See merge request gitlab-org/gitlab!37290

Add more specific ID type for DastSiteProfiles

See merge request gitlab-org/gitlab!38660

[RUN AS-IF-FOSS] Mount PersonalAccessTokens API in EE only

See merge request gitlab-org/gitlab!38865

Disable loading resolvedOnDefaultBranch for Vulnerabilities

See merge request gitlab-org/gitlab!38783

Geo: Part 2 of Enforce not null merge_request_diffs.external_diff_store

See merge request gitlab-org/gitlab!38719

Use Express template for auto devops app

See merge request gitlab-org/gitlab!38683

On GitLab.com, 19M of 93M rows have NULL external_diff_store.

With batches of 5000 and a background migration job interval of 2m 5s,
3.8K jobs are scheduled over 5.5 days.

The index `index_merge_request_diffs_external_diff_store_is_null` is
expected to be used by the migration queries.

queue_background_migration_jobs_by_range_at_intervals is not used
because it would enqueue 18.6K jobs and we have an index for getting
these ranges.

Replace fa-cubes icon with GitLab SVG package icon

Closes #225200

See merge request gitlab-org/gitlab!38664

Merge branch '227582-package-detail-ui-update-the-package-detail-main-body-to-include-a-history-install-commands' into 'master'

New Package details UI

See merge request gitlab-org/gitlab!38680

- new component
- tests

Fix problem that vulnerability list is not loaded

See merge request gitlab-org/gitlab!38867

Add PipelineArtifact table and model

See merge request gitlab-org/gitlab!37969

This new model will be used to store generated report consumable
by gitlab frontend in a pipeline context.

Fix for project_security_dashboard_spec

Closes #233362

See merge request gitlab-org/gitlab!38509

Index trial groups in Elasticsearch

Closes #225744

See merge request gitlab-org/gitlab!38541

Add a licence_compliance_spec end to end test

See merge request gitlab-org/gitlab!38598

Add e2e test of distributed reads from unhealthy node

Closes gitlab-org/quality/testcases#859

See merge request gitlab-org/gitlab!37664

The endpoint is EE only, so must be mounted only in the EE API class
(see https://gitlab.com/gitlab-com/gl-infra/production/-/issues/2495
for this breaking)

Allow saving of runbooks to PrometheusAlert

See merge request gitlab-org/gitlab!38234

Improve details on duplicate pipelines

See merge request gitlab-org/gitlab!36009

Fix: Correct SAST docs variable groupings

See merge request gitlab-org/gitlab!38816

Move constants to constant file for suggest pipeline

Closes #229937

See merge request gitlab-org/gitlab!38616

- better development pattern.

Revert "Create emphemeral IssueLink if Feedback is present"

Closes #223770

See merge request gitlab-org/gitlab!38785

Document `-writable` flag of Praefect's dataloss

See merge request gitlab-org/gitlab!38796

Create freeze period frontend fixture

See merge request gitlab-org/gitlab!38525

Remove signup experiment tracking

See merge request gitlab-org/gitlab!38801

As part of https://gitlab.com/gitlab-org/gitlab/-/issues/220386 we want
to index trial groups in Elasticsearch so they can make use of Advanced
search.

This change also refactored the existing logic around indexing paid
groups a bit:

1. Removing the feature flag that has been on for a while now along
with the documentation explaining this feature flag. We already have
separate docs explaining that Advanced Global Search is enabled for
bronze and above groups so this is not necessary.
2. This will now also exclude `expired?` groups which we shouldn't have
been indexing to begin with. The assumption is that the `expired?` check
will also ensure we skip expired trials. These expired trials also have
a `trial_ends_on` date but based on looking at some data I think we can
expect this will be the same or less than `end_date`. The expired trials
that are in the index will be cleaned up in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/38551
3. Don't check `saved_changes.key?('hosted_plan_id')` anymore since we
don't really care why the plan is changing. As long as we use
`safe_find_or_create_by!` we'll be fine to run this multiple times.

This reverts commit 76eb2c96, reversing
changes made to 67739c5b.

It appears that GraphQL can't handle records which have id of nil, we
need to revert this change as it prevents our API from working while we
think of a workaround.