Implement allowing empty needs for jobs in DAG pipelines

See merge request gitlab-org/gitlab!22246

Increase pipeline email notification from 10 to 30 lines

See merge request gitlab-org/gitlab!21728

Add subepics feature to license and services

See merge request gitlab-org/gitlab!24170

[UPDATE] Migrating `fa-spinner` from `app/views/shared/notifications`

Closes #204742

See merge request gitlab-org/gitlab!24940

Add GET endpoint to LDAP group link API

Closes #13679

See merge request gitlab-org/gitlab!24216

Add delete identity API endpoint to users API

Closes #23068

See merge request gitlab-org/gitlab!24122

This will allow jobs to have "needs: []" configuration.
Those jobs will start immediately without waiting previous stages

Scope merge request approval rules to protected branches using API search

Closes #460

See merge request gitlab-org/gitlab!24344

Migrate fa-spinner to spinner in milestones directory

See merge request gitlab-org/gitlab!25067

Moves the standalone vulnerabilities url to `/vulnerabilities/[id]`"

See merge request gitlab-org/gitlab!24777

- Moves the url from /security/dashboard/[id] to
  /security/vulnerabilities/id
- Moves the nessecary bits from the dashboard controller to the
  vulnerabilities controller
- Remaps the vulnerability_path routing helper to match the above
  changes
- Updates the tests to match the above changes

Fix autocomplete limitation bug – take 2

See merge request gitlab-org/gitlab!25167

Separate platform provider and post receive entities into own class files

See merge request gitlab-org/gitlab!25119

Allow config of sidekiq-cluster with query

Closes gitlab-com/gl-infra/scalability#45

See merge request gitlab-org/gitlab!18877

Show Kubernetes namespace on job show page

Closes #31756

See merge request gitlab-org/gitlab!20983

Adds support for showing kubernetes namespaces on deployment jobs where
the namespace has been recorded.

See https://gitlab.com/gitlab-org/gitlab/issues/31756

Also fixes a bug where we were using the last successful deployment
instead of the deployment associated with the build to determine which
cluster to display.

Resolve "Follow-up from "Add Windows Shared Runners to GitLab.com docs""

Closes #198013

See merge request gitlab-org/gitlab!25020

Resolve discussion in issue 198013.
- Reworded section describing usage quotas.

Update dependency @gitlab/ui to ^9.8.0

See merge request gitlab-org/gitlab!24862

[UPDATE] updated underscore to lodash in spec/javascripts/badges

Closes #196678

See merge request gitlab-org/gitlab!25135

Design view: moveable "new comment" pin

See merge request gitlab-org/gitlab!24769

- and emit the appropriate noteMove and openCommentForm events

Replace underscore with lodash for ./app/assets/javascripts/ci_variable_list

Closes #196663

See merge request gitlab-org/gitlab!25174

Replace underscore with lodash for ./app/assets/javascripts/contributors

Closes #196638

See merge request gitlab-org/gitlab!25027

Partially migrate ee/spec/javascripts/environments/ to Jest

See merge request gitlab-org/gitlab!24995

Merge branch '202592-migrate-fa-spinner-to-spinner-for-app-views-admin-application_settings' into 'master'

Migrate '.fa-spinner' to '.spinner' for admin/application_settings

Closes #202592

See merge request gitlab-org/gitlab!24880

Add projects widget to instance security dashboard

See merge request gitlab-org/gitlab!24644

Adds Security::VulnerableProjectsController and accompanying route,
which reuses the logic backing the vulnerable projects widget on the
group security dashboard.

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

Docs update note for external id and kube-ctl

See merge request gitlab-org/gitlab!25206

jQuery at.js has a hard limit on how many items can be searched. Before
it executes it's search function, it limits the array size to 1000
items. We have been hitting this bug because we have more than a
thousand users or labels [0][1].

We are planning to replace at.js [2], but in order to fix this bug for
now, we have forked at.js [3] and made adjustments, so that it works for
our usecases.

Performance wise this should have no big impact, as we are rendering a
maximum of 5 results in the most cases anyway. The search on the
javascript side is rather performant.

[0]: https://gitlab.com/gitlab-org/gitlab/issues/204825
[1]: https://gitlab.com/gitlab-org/gitlab/issues/198650
[2]: https://gitlab.com/gitlab-org/gitlab/issues/27240
[3]: https://gitlab.com/gitlab-org/frontend/At.js