Add missing spec for fogbugz importer

See merge request gitlab-org/gitlab!20981

Do not attribute unverified commit e-mails to GitLab users

Closes #28493

See merge request gitlab-org/gitlab!21214

Add two partial nonunique indexes

See merge request gitlab-org/gitlab!21230

- Non-unique

Update RSpec helper methods to *_next_instance_of

See merge request gitlab-org/gitlab!21244

Convert Web IDE specs to jest

See merge request gitlab-org/gitlab!21153

Fix Sidekiq testing API warnings in Rake tasks

Closes #38377

See merge request gitlab-org/gitlab!21343

Cleanup API GET service endpoint

See merge request gitlab-org/gitlab!21310

Add warning dialog when users click "Merge immediately" merge train option

Closes #12679

See merge request gitlab-org/gitlab!20054

Link to suggested community contributions

See merge request gitlab-org/gitlab!21345

Add security configuration navigation item

See merge request gitlab-org/gitlab!20711

This commit adds a new navigation item to the main navigation. It
sits within a project's "Security & Compliance" submenu and
links to the security configuration screen.

These files were updated automatically with this script:

```
result="$(awk '/[{\[]$/ { printf("%s\t", $0); next } 1' $1)"
echo "$result" > $1
yarn prettier --write $1
```

Includes related import reordering for IDE-related
files to fix eslint warnings.

See issue https://gitlab.com/gitlab-org/gitlab/issues/29243
which tracks the overall effort for migration to Jest.

Running any Rake task would show:

ARNING: Sidekiq testing API enabled, but this is not the test
environment.  Your jobs will not go to Redis.

To fix this, we move the `require` statement into the import task.
Now this message only shows when running the import job.

Closes https://gitlab.com/gitlab-org/gitlab/issues/38377

Increase experiment ratio

See merge request gitlab-org/gitlab!21303

Add the command for restarting GitLab helm chart

See merge request gitlab-org/gitlab!20214

Adds missing spec for fogbugz importer

Add new help text to sentry settings

Closes #34058

See merge request gitlab-org/gitlab!20663

Update eslint-plugin-import from 2.16.0 to 2.18.2 (/spec/javascripts/ide)

See merge request gitlab-org/gitlab!21304

Auto-correct some references in RSpec as:
- expect_any_instance_of -> expect_next_instance_of
- allow_any_instance_of -> allow_next_instance_of

Related to https://gitlab.com/gitlab-org/gitlab/issues/34997

Fix misleading comment

See merge request gitlab-org/gitlab!21255

Resolve "Document  - Make using GitLab auth with Vault easy" - documentation

Closes #9983

See merge request gitlab-org/gitlab!19980

Add changelog

Fix pipeline retry in a CI DAG

Closes #36068

See merge request gitlab-org/gitlab!21296

Refinements to the intro section

See merge request gitlab-org/gitlab!21217

Keyset pagination on primary key

See merge request gitlab-org/gitlab!21194

This commit adds a warning dialog after the user clicks the "merge
immediately" merge train option asking them to confirm their choice.

This dialog contains a link to the documentation as well as some text
about why merging immediately may not be the best choice.

Resolve "Add "updated_after" parameter to the Pipelines API endpoint"

Closes #33099

See merge request gitlab-org/gitlab!21133

Allow raw blobs to be served from an external storage

See merge request gitlab-org/gitlab!20936

Use `without_count` for audit event records paginated with `paginate_without_counts`

See merge request gitlab-org/gitlab!21232

We used to return service password for admin users.
This has been removed as part of a security fix
and this commit removes some leftover of this feature

* API::Helpers::Pagination#paginate only exposes offset pagination
* API::Helpers::Pagination#paginate_and_retrieve! supports both types

I wanted to make it explicit that keyset pagination returns an array
instead of a relation. This does not match the behavior of offset
pagination, hence not mixing those in #paginate.

Previously a retried pipeline for builds in a DAG would cause the newly-
created builds to sit in the created state because it would be waiting
for the dependencies to trigger it. However, in the retry case, the
dependencies may have already completed, so they will never trigger new
builds.

We fix this by:

1. Looking up successful builds with the required names
2. Passing those build IDs to `Ci::ProcessPipelineService` to trigger
   builds with those dependencies.

Closes https://gitlab.com/gitlab-org/gitlab/issues/36068

Refactor project API helpers

Closes #37919

See merge request gitlab-org/gitlab!21130