Fix duplicate spec in merge requests

See merge request gitlab-org/gitlab!28856

Fix duplicate spec in closing issue specs

See merge request gitlab-org/gitlab!28803

Move Prometheus metrics services to Core

See merge request gitlab-org/gitlab!28523

Fixed incorrect name

See merge request gitlab-org/gitlab!28880

Adds parent_pipeline to CI_PIPELINE_SOURCE

See merge request gitlab-org/gitlab!28441

Resolve Migrate '.fa-spinner' to '.spinner' for 'app/views/projects/network'

See merge request gitlab-org/gitlab!25050

Bump workhorse version to 8.30

See merge request gitlab-org/gitlab!28894

Quarantine flaky test

See merge request gitlab-org/gitlab!28887

This enables support for proxying ActionCable connections

Clean up linting information

See merge request gitlab-org/gitlab!28878

Skip generating smaller Design Management designs for TIFFs

See merge request gitlab-org/gitlab!28875

Track jira import state in its own data structure

See merge request gitlab-org/gitlab!28709

The test fails intermittently in master
See https://gitlab.com/gitlab-org/gitlab/-/issues/213222

Changing offline terminology to offline environments

See merge request gitlab-org/gitlab!28594

Update IP allocation details

See merge request gitlab-org/gitlab!28599

Document gitlab qa mirror downstream project

See merge request gitlab-org/gitlab!28559

Remove pages_internal_api feature flag

See merge request gitlab-org/gitlab!28546

Add notes about (not) including screenshots in QA failure issue

See merge request gitlab-org/gitlab!28708

Normalize signature mime types when filtering attachments in emails

See merge request gitlab-org/gitlab!28865

Fixes filtering when a MUA mixes 'x-' prefixed and non prefixed mime
types in signatures

Docs for using flags with GraphQL field values

See merge request gitlab-org/gitlab!28737

Updating the GraphQL API Styleguide to describe how to use feature flags
when a developer wants to toggle the value of a field.

This change came out of a Slack conversation in `#f_graphql` where a
developer wished to use an actor-based gate.

Documentation: Make NFS server delegation recommendation clearer

See merge request gitlab-org/gitlab!28761

Make all field examples in GraphQL docs nullable

See merge request gitlab-org/gitlab!28739

Change GraphQL milestone property to be a String

See merge request gitlab-org/gitlab!28736

Update issues export documentation screenshot

See merge request gitlab-org/gitlab!28799

Remove (deprecated) strings from ProjectType

See merge request gitlab-org/gitlab!28735

Fix export issues feature screenshot documentation

An issue with using `Float`s to define the `milestone` of a deprecated
field surfaced with the milestone 12.10. As a `Float`, this becomes
`"12.1"`.

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28560#note_316709552

Changing the documentation and all uses of `milestone` to be `String`s

ProjectType had (deprecated) added to the description of some of its
fields in d1451e7b. These were added because the same properties had
been deprecated in the REST Projects API in favor of properties called
`{x}_access_level`
https://gitlab.com/gitlab-org/gitlab/-/issues/211620#note_315174858.

As the GraphQL ProjectType does not have such fields, the fields that
had "(deprecated)" added to their descriptions were never actually
deprecated.

This MR removes those strings, and also makes the descriptions more
consistent according to
https://docs.gitlab.com/ee/development/api_graphql_styleguide.html#description-styleguide:

> Descriptions of GraphQL::BOOLEAN_TYPE fields should answer the
> question: “What does this field do?”. Example: 'Indicates project has
> a Git repository'.

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

Fix yaml spacing in junit doc

Closes #213294

See merge request gitlab-org/gitlab!28747