Fix pdf.js rendering pages in the wrong order

Closes #64467

See merge request gitlab-org/gitlab-ce!31222

Resolve EE specific differences in the spec/ directory

See merge request gitlab-org/gitlab-ce!31109

EE: Resolve EE specific differences in the spec/ directory

See merge request gitlab-org/gitlab-ee!14823

Replace peek-pg with our own implementation

Closes #44441

See merge request gitlab-org/gitlab-ce!31187

Instead of complicated splicing, we can simply return all pages.
Promise.all will take care of the correct ordering for us.

Resolve "Add new documentation and link for automating Visual Review feedback"

Closes #12447

See merge request gitlab-org/gitlab-ee!14789

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

Resolve "Support runtime Visual Review configuration"

See merge request gitlab-org/gitlab-ce!30481

* adds the ability to enter a merge request ID directly into the toolbar,
* adds the option to save the ID to `localStorage` (as with the token),
* adds a link to change the ID once entered
* adds some more explanatory errors for 401 & 404
* saves the comment to session storage if the user navigates away without posting it

There was an implicit assumption that the pages returned from the
Promise of `pdf.getPage(num)` would return in order, but no such
guarantee exists. To handle this, we explicitly set which array index
based on the page number and then trigger a Vue update via `splice`.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64467

LDAP rake task to run a GroupSync

Closes #13089

See merge request gitlab-org/gitlab-ee!14735

Backport EE changes made to the scripts/ directory

See merge request gitlab-org/gitlab-ce!31015

EE: Backport EE changes made to the scripts/ directory

See merge request gitlab-org/gitlab-ee!14778

Pass alert bot user when creating incidents

See merge request gitlab-org/gitlab-ee!14860

Previously, we passed `nil` as `current_user` to
`IncidentManagement::CreateIssueService.new` and used `issue_author`.

After this commit we pass `User.alert_bot` explicitly and utilize
`current_user` in the service as usual.

[ci skip]

[ci skip]

Update reference architecture docs to remove status

Closes gitlab-org/quality/performance#14

See merge request gitlab-org/gitlab-ce!31077

Fix EE namespacing of DesignsCounterService

See merge request gitlab-org/gitlab-ee!14881

CE: Add project download & project export audit event

See merge request gitlab-org/gitlab-ce!31103

Further remove `if postgresql?` branches

Closes #65054

See merge request gitlab-org/gitlab-ce!31102

EE had a slightly different audit spec. In this commit we use the CE
code for the shared spec, and move the EE specific spec to a separate
spec file.

Extract security dashboard permissions

See merge request gitlab-org/gitlab-ee!14754

This commit extracts the controller logic for security dashboard
permissions so that we can reuse it in the upcoming project security
dashboard controllers.

This comment exists in CE, but not in EE.

This moves the specs for ObjectHierarchy#root to a separate spec file,
ensuring the file shared between CE and EE is the same for both.

Merge branch '12690-use-all-pipelines-instead-of-ci-pipelines-in-security-dashboard-code' into 'master'

Use `all_pipelines` instead of `ci_pipelines` in Security Dashboard

Closes #12690

See merge request gitlab-org/gitlab-ee!14854

This ensures this spec is the same in both CE and EE.

This changes the spec in question so that it is the same for both CE and
EE. This requires an `if Gitlab.ee?` since EE requires that we stub an
EE specific module, but doing so in CE will break the spec there.

This changes a protected tags feature spec so that it is the same in
both CE and EE. This requires the use of a `if Gitlab.ee?` check, as the
added lines don't work in CE but do work in EE. Removing them entirely
in turn breaks the EE spec.