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

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

Reversible migration helper

See merge request gitlab-org/gitlab!16762

Can be used to test the reversibility of migrations.

Clean up project export error logging

See merge request gitlab-org/gitlab!17780

Update webpack dependencies

Closes #32616

See merge request gitlab-org/gitlab!17560

Documentation update about Export CSV

See merge request gitlab-org/gitlab!17763

Updated directions for associating a namespace

See merge request gitlab-org/gitlab!17280

Provide metrics dashboard path to cluster health chart

See merge request gitlab-org/gitlab!17648

This makes it so we provide `dashboard-endpoint` to cluster health
charts. This is needed so the frontend knows where to fetch cluster
dashboards.

Unflake unassign test

Closes #32621

See merge request gitlab-org/gitlab!17627

Operations Dashboard: fix minimum query message

Closes #32628

See merge request gitlab-org/gitlab!17574

Moves Protected paths throttling from Omnibus to GitLab Rails

See merge request gitlab-org/gitlab!16463

- Adds 4 columns to application_settings
  - 3 to mimic the configuration of existing throttles
  - 1 to store the protected paths on database
- Set default protected paths (taken from Omnibus)
- Add new section on admin panel to personalize protected paths
configuration
- Includes additional protected paths throttles.
- Throttles were renamed to 'rack_attack_gitlab_rails'.rb, otherwise the
omnibus file will overwrite this file.
- If the Omnibus throttle is enabled, this settings will not take
effect.