If the import version changes, we need to update a few project templates
to match this new version.

In a seperate commit I'll update the docs to reflect this.

This finishes the procedure for migrating events from the old format
into the new format. Code no longer uses the old setup and the database
tables used during the migration process are swapped, with the old table
being dropped.

While the database migration can be reversed this will 1) take a lot of
time as data has to be coped around 2) won't restore data in the
"events.data" column as we have no way of restoring this.

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241

Clean up new navigation templates

See merge request !13983

Fix wrong API status codes

See merge request !14069

Resolve "Update the docs for GPG for gpg2 - [secret key not available]"

Closes #36859

See merge request !14024

Update 'Visibility of pipelines'

Closes #34360

See merge request !13948

Move Incoming Email checks to System Checks

See merge request !14028

Use flexbox for prometheus graph row grouping instead of bootstrap classes

See merge request !14006

Optimize Groups::GroupMembersController#create

Closes #27374

See merge request !13825

Migrate old issues without author to the ghost user

Closes #36860

See merge request !13860

Enable all gitaly features in spinach tests

Closes gitaly#521

See merge request !14043

Make search dropdowns consistent

See merge request !13615

Update issue search example to lorem ipsum

See merge request !14057

Change hint format for main filtered search dropdown

Closes #29786

See merge request !13895

Docs update confidential system note

See merge request !14063

Navigation updates

Closes #35424 and #35091

See merge request !13480

Remove GraphQL from future plans.

See merge request !14060

The following optimizations were performed:

- Add new association to GroupMember and ProjectMember

  This new association will allow us to check if a user is a member of a
  Project or Group through a single query instead of two.

- Optimize retrieving of Members when adding multiple Users

Bump jira-ruby gem to 1.4.1 to fix issues with HTTP proxies

Closes gitlab-ee#3125

See merge request !13617

Cleanup rspec_flaky report files in the update-tests-metadata job

See merge request !14056

Migrate Gitlab::Git::Repository#find_branch to Gitaly

Closes gitaly#502

See merge request !13873

Previous versions of jira-ruby gem would generate erroneous URLs when an HTTP
proxy were confused via the `http_proxy` environment variables:
https://github.com/sumoheavy/jira-ruby/issues/250

Closes gitlab-org/gitlab-ee#3125

# Conflicts:
#   db/schema.rb

API: Add GPG key management

Closes #36926

See merge request !13828

Signed-off-by: Rémy Coutable <remy@rymai.me>

Fuzzy search issues / merge requests

Closes #26835, #29994, and #20362

See merge request !13780

Remove project select dropdown from breadcrumb

Closes #35010

See merge request !14010