When a due date falls on the current date,
it should not be considered expired.

- Convert the sort argument to string so symbol can be
additionally used.

expiredLast is more appropriate
as a sort option since it is a specialized
case of due date sorting.

- Annotate using :aggregate_failures over wrapping in blocks
- DRY creating objects and specs

These changes are made to milestone-related GraphQL APIs.

- Milestone type gets a new 'expired' field indicating
whether milestone's due date is past the current date.

- When listing milstones, these arguments can be specified:

  - 'expiredLast' sorts milestones in layers:
  Current miletones are placed first, followed by
  milestones without due dates and expired milestones.
  Within layers, milestones are sorted by due date
  (asc by default) with ties being broken by id (desc).
  When 'expiredLast' is set, 'sort' argument other than
  due_date_desc or due_date_asc is ignored.

  - 'sort'

Changelog: added

A new method is added to the milestone model
to support fetching milestones in this particular order:
1. Current milestones (due date > current date)
2. Milestones without due dates
3. Milestones that are expired (due date <= current_date)

The milestones are then sorted by due date (asc or desc)
and ties are broken by id in descending order.

The milestone finder is also updated to accept
a new Boolean parameter 'expired_last' to utilize the
newly added custom ordering to fetch milestones.

When 'expired_last' is specified, order param must be
one of 'due_date_asc' or 'due_date_desc'. For non-supported
order param values (including when it's not provided),
the default is 'due_date_asc'.

Refactor to use let_it_be and build wherever suitable
to improve test performance.

Give definitions to each of the repository storage move states

See merge request gitlab-org/gitlab!65288

Respect protected tag in release permissions

See merge request gitlab-org/gitlab!64693

Add target branch in pipeline editor for blank projects

See merge request gitlab-org/gitlab!64575

Use default_enabled for feature flag check

See merge request gitlab-org/gitlab!65212

Update docs wrt. author of commit applying suggested changes

See merge request gitlab-org/gitlab!64570

Add troubleshooting section for Bitbucket

See merge request gitlab-org/gitlab!64602

Present error when DAST profile not found

See merge request gitlab-org/gitlab!64679

- Add new code that adds to Ci::Pipeline#yaml_errors
- Update specs accordingly

Changelog: changed

Stkerr update compliance metrics

See merge request gitlab-org/gitlab!62413

Drop full index on ci_builds.token

See merge request gitlab-org/gitlab!65025

Add link instrumentation in readme markdown templates

See merge request gitlab-org/gitlab!64564

Document 'object_attributes.action' for issue, MR, and release webhooks

See merge request gitlab-org/gitlab!65177

Improve security merge request template

See merge request gitlab-org/gitlab!65282

Docs: Group level webhooks do not have logs

See merge request gitlab-org/gitlab!65162

Fix grammar mistakes in Geo replication FAQ

See merge request gitlab-org/gitlab!65240

Add meta fields to email receiver error

See merge request gitlab-org/gitlab!65001

Improve LoadBalancer#all_caught_up? logic [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!65248

Move experiment tracking behavior to configuration

See merge request gitlab-org/gitlab!65179

Move prometheus service creation to the background job [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!63539

Highlight and explain why that the security issue must be linked to the
release tracking issue. This may help eliminate confusion that assigning
to the release bot is enough.

Debian package registry documentation

See merge request gitlab-org/gitlab!64649

Add debian registry documentation
Add debian distribution API documentation
Add debian API documentation

Allow incident severity updates to trigger issue webhooks

See merge request gitlab-org/gitlab!64748

Remove use of 'service' term from integration model specs

See merge request gitlab-org/gitlab!65033

Remove project from Job Token Scope via GraphQL

See merge request gitlab-org/gitlab!64522

- Introduce service object to remove project from scope
- Use new service object in new GraphQL mutation

Changelog: added