Add reliable sidekiq fetcher

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

Resolve "More N+1s in calculating notification recipients"

Closes #47496

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

Change image for docs linting

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

Resolve "Unable to close performance bar"

Closes #50552

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

Fix markdown table border and background color

Closes #52178

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

Improve the MR documentation

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

Resolve "Error while updating todo status: the button is stuck in the loading state"

Closes #48222

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

Add subscribe filter to labels page

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

If we don't call #to_a, we're relying on the members already being loaded from
elsewhere. Otherwise we'll do a separate query for each user:

    [1] pry(main)> Project.first.team.members.include?(User.first)
      Project Load (0.7ms)  SELECT  "projects".* FROM "projects"  ORDER BY "projects"."id" ASC LIMIT 1
      ↳ (pry):3
      User Load (1.8ms)  SELECT  "users".* FROM "users"  ORDER BY "users"."id" ASC LIMIT 1
      ↳ (pry):3
      User Exists (0.6ms)  SELECT  1 AS one FROM "users" INNER JOIN "project_authorizations" ON "users"."id" = "project_authorizations"."user_id" WHERE "project_authorizations"."project_id" = $1 AND "users"."id" = $2 LIMIT 1  [["project_id", 1], ["id", 1]]
      ↳ (pry):3
    => true
    [2] pry(main)> Project.first.team.members.to_a.include?(User.first)
      Project Load (12.8ms)  SELECT  "projects".* FROM "projects"  ORDER BY "projects"."id" ASC LIMIT 1
      ↳ (pry):1
      User Load (9.6ms)  SELECT "users".* FROM "users" INNER JOIN "project_authorizations" ON "users"."id" = "project_authorizations"."user_id" WHERE "project_authorizations"."project_id" = $1  [["project_id", 1]]
      ↳ (pry):1
      User Load (0.6ms)  SELECT  "users".* FROM "users"  ORDER BY "users"."id" ASC LIMIT 1
      ↳ (pry):1
    => true

Backport EE merge spec changes

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

Renders empty states in the Vue app in Job page

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

Clone nurtch demo notebooks at Jupyter startup

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

Support short reference to epics from project entities

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

Remove addtionalProperties in runners schema

Closes #52195

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

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

Add signature badge and pipeline status to commit details in MR diff

Closes #49329

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

Fix links to external site and minor Markdown improvements

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

Port: Add checks to InterpretService conditions

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

Add a QA spec for RBAC cluster and auto devops

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

Fix environment name overlapping

Closes #52065

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

Fix faulty resolution of babel-messages in yarn.lock

Closes #52192

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

Instance Configuration page now displays correct SSH fingerprints

Closes #40636

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

Show percentage of language detection on the language bar

Closes #51457

See merge request https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22056

Fix todo cops

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

I don't know if the issue [0] was caused by a faulty merge, or why, but
it seems like babel-messages had the wrong URL in there and resolved to
babel-plugin-transform-object-rest-spread, which is wrong.

So the integrity check did actually work and catch that!

[0]: https://gitlab.com/gitlab-org/gitlab-ce/issues/52192

Simplify runner registration token resetting

Closes #41922

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

Adds MR reference in job sidebar

Closes #52191

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

These can be triggered by project creation in the setup phase if a spec uses the
RequestStore, but we really don't care about that - it's not an N+1, it's just
several projects being created!

This isn't called from anywhere.

This fails now because we have not yet implemented support for this