Fix button link foreground color

Closes #34240

See merge request gitlab-org/gitlab!18669

Change `IS_GITLAB_EE` to `FOSS_ONLY`

Closes #33875

See merge request gitlab-org/gitlab!18517

Revert "Merge branch '13034-update-dast-report-fixture' into 'master'"

Closes #34216

See merge request gitlab-org/gitlab!18670

Updated Epic docs

See merge request gitlab-org/gitlab!17297

- Updated Epic overview screenshot
- Updated Roadmap tab screenshot
- Updated Epics list view screenshot
- Moved like topics together
- Changed some admonitions to text
- Simplified several procedures' steps

Merge branch '34211-use-a-fixed-version-of-the-gitlab-charts-in-our-review-app-deployments' into 'master'

Use a fixed version of the GitLab charts in our Review App deployments

Closes #34211

See merge request gitlab-org/gitlab!18653

Resolve "Update issue list icons"

Closes #32380

See merge request gitlab-org/gitlab!18226

Improve service level health-checks

See merge request gitlab-org/gitlab!18665

Load signature only for last commit on blob#show

See merge request gitlab-org/gitlab!18573

Run FOSS system tests and simplify dependencies

See merge request gitlab-org/gitlab!18222

* We also use `needs` to speed it up
* To simplify the dependencies, we also pull cache on master

This commit fixes a regression that caused button links to render with a
dark foreground instead of a white foreground.

Remove custom merge strategy for db/schema.rb

See merge request gitlab-org/gitlab!18406

Add API for manually creating deployments

Closes #25176 and #32579

See merge request gitlab-org/gitlab!17620

Feature #19822, users can preview audio in a repository.

See merge request gitlab-org/gitlab!18354

Change design management empty state button style

See merge request gitlab-org/gitlab!18060

https://gitlab.com/gitlab-org/gitlab/issues/13395

Fix links to all redirected blog posts

See merge request gitlab-org/gitlab!18586

Fix all links to blog posts to use the new
path of about.gitlab.com/blog

Adjust test to avoid flakiness

Closes #34144

See merge request gitlab-org/gitlab!18657

Correct validation backlog label name in issue template

See merge request gitlab-org/gitlab!18595

Add section about experiments

See merge request gitlab-org/gitlab!17538

This reverts merge request !17778

This API can be used for manually creating deployments, instead of being
limited to creating deployments using CI pipelines.

As part of these changes, I refactored some parts of the existing
deployments code. This ensures we reuse the same logic for creating
deployments in different places. We also move the deployments service
classes to a Deployments namespace, now that there are two service
classes.

We also make some changes to which deployments are displayed. Prior to
these changes, only deployments that were successful were displayed.
This can get very confusing when using deployments from external
systems, so we now show deployments regardless of their status. The
table to display deployments has also had some style/content changes to
display the deployments data in a more meaningful way.

Add `on_before_phased_restart` lifecycle event

See merge request gitlab-org/gitlab!18582

Unicorn/Puma Cluster: This will be called before a graceful
shutdown of workers starts hapepning.
This is called on `master` process.

Support Create/Read/Destroy operations in Feature Flag API

See merge request gitlab-org/gitlab!18198

Fix caching of submodule links for shas with dashes

See merge request gitlab-org/gitlab!18576

This removes the usage of IS_GITLAB_EE
and prefer to use FOSS_ONLY that has
the following states:
1. nil/empty string: use CE or EE depending on sources
1. false: use CE or EE depending on sources
2. true: use CE always

Replace index on ci_triggers

See merge request gitlab-org/gitlab!18652

Resolve "Follow-up from "Handle tag delete 404""

Closes #34196

See merge request gitlab-org/gitlab!18641

Add additional scopes to note

See merge request gitlab-org/gitlab!18309

This improves the behavior of health-checks
introducing two levels of them:

- service level: checks served by `sidekiq|web_exporter:'
  served on separate port

- application level: checks served by `/-/metrics` endpoint
  of `HealthController`

The changes makes the:

- `/liveness` always indicate that application is ready
  and not deadlocked
- `/readiness` to indicate:

The changes for `/readiness`:

- on service level: the status of the service if it can accept
  and process connections

- on application level: the status of external components if they
  are accessible

The `on service level` and `on application level` do not share
any checks, they have different checks exposed.

Add blackout period support for `web_exporter:`

See merge request gitlab-org/gitlab!17962

This introduces `#run_thread` method.

The `#start_working` is executed in lock context,
the same as `#stop_working`. This allows safe
initialisation of resources before `#run_thread`
consumes them.