Update 404 and redirecting links in /development

See merge request gitlab-org/gitlab!17734

Update all links in /dev that were causing 404s
or redirecting warnings in the link checker

Update caps and backticks in /topic /workflow /university

See merge request gitlab-org/gitlab!17653

Update capitalization and backtick use in /topic
/university and /workflow

Remove nested Promise from notes actions

See merge request gitlab-org/gitlab!17686

Add proper token check for Notify Service

Closes #14792

See merge request gitlab-org/gitlab!17759

Migrate confidential_issue_sidebar_spec.js to Vue test utils

See merge request gitlab-org/gitlab!17552

Remove nested Promise from board blank state

See merge request gitlab-org/gitlab!17684

Refactored Karma spec to Jest for todo_spec.js

Closes #31306

See merge request gitlab-org/gitlab!16733

Extract base filter constant in Securitty Dashboard store's filters module

See merge request gitlab-org/gitlab!17710

Remove nested Promise from admin email select

See merge request gitlab-org/gitlab!17689

Refactor Security Dashboard store

See merge request gitlab-org/gitlab!17250

This refactoring is part of the [Instance Security Dashboard MVC][1], to
abstract away from the base Security Dashboard the logic for how the
list of projects to filter with is set. It:

* Adds a new `GroupSecurityDashboard` component that wraps the
  `SecurityDashboard` component.
* Moves the `projects` module bindings/calls from the
  `SecurityDashboard` component to the new `GroupSecurityDashboard`.
* Creates a new `projects` plugin for the Security Dashboard store which
  dynamically adds the `projects` module and sets up the appropriate
  store bindings between it and the `filters` module.
* Updates the entry point for the Group Security Dashboard to add the
  `projects` plugin to the Security Dashboard store.
* Moves the existing `mediator` and `sync_with_store` plugins into
  a `plugins` directory.
* Renames `moderator` to `mediator`.

[1]: https://gitlab.com/gitlab-org/gitlab/issues/6953

Add frozen_string_literal to all ee specs

See merge request gitlab-org/gitlab!17754

Adding step to ensure author includes rollback information

See merge request gitlab-org/gitlab!17537

Update 404 / Redirected links in monitoring, install, security

See merge request gitlab-org/gitlab!17795

Update all links throwing 404 or redirect messages
in the docs project link checked, for monitoring,
install and security docs.

Remove nested Promise from project select

See merge request gitlab-org/gitlab!17687

Export design management data with project export

Closes #11090

See merge request gitlab-org/gitlab!14702

Docs - Add note about env slugs being immutable

See merge request gitlab-org/gitlab!16592

Export design repository in project export

See merge request gitlab-org/gitlab!14700

[Frontend] Show success banner to user when trial starts

See merge request gitlab-org/gitlab!16794

https://gitlab.com/gitlab-org/gitlab-ee/issues/11090

https://gitlab.com/gitlab-org/gitlab-ee/issues/11090

https://gitlab.com/gitlab-org/gitlab-ee/issues/11090

Moving a group of shared_examples from project_tree_restorer_spec to
its own file in spec/support/shared_examples in order for these examples
to be reused in an EE-specific test.

https://gitlab.com/gitlab-org/gitlab-ee/issues/11090

Making the code of the markdown table the same as the rendered example

See merge request gitlab-org/gitlab!17619

Update oidc.md

See merge request gitlab-org/gitlab!17566

Add UI text label to "Issues workflow" Contributing doc

See merge request gitlab-org/gitlab!17622

As specs failed which will require app-level changes to fix.

Fix design flaky specs

See merge request gitlab-org/gitlab!17654

Some specs that create a design with a `with_file` trait would fail
intermittently with a Gitaly error `A file with this name already
exists`. This signalled that a collision in the design.full_path in
the spec. The full_path is made from the id of the issue and its name.

The failing tests would fail when a `create(:design, :with_file)` was

- created in a `before` block
- its issue was created in a `set`
-  and it was setting a specific filename for the design.

In this situation, if a capybara spec failed once, it would retry again,
and would try to create a design with the same name and save it against
the same issue from the last time it ran. This would lead to a full_path
conflict.

The fix is a combination of:
- using the default (dynamically sequenced) filenames for designs that
  are generated by FactoryBot where possible
- if we do set a design that has a `with_file` trait (meaning it will
  create an underlying commit in Gitaly for the design version) then the
  issue must be created at the same time as the design is within the
  test

See https://gitlab.com/gitlab-org/gitlab/issues/32620#note_222564584