Add latest pipelines link to api

See merge request gitlab-org/gitlab!16534

Add zoom call section in Issue docs

See merge request gitlab-org/gitlab!16836

Add npm metadata tags table

See merge request gitlab-org/gitlab!15770

Tables for metadata and package tags

Fix typo in group name in ldap-ee.md

See merge request gitlab-org/gitlab!16881

Fix docker code block formatting in ADO docs

See merge request gitlab-org/gitlab!16899

Upgrade gitlab-pages to 1.9.0

See merge request gitlab-org/gitlab!16801

Enabling runners token for groups

See merge request gitlab-org/gitlab!16831

Issue #60774 : I understand the limitations on the number of queries as a test but don't understand how can I count them yet. I'll try to see if I can progress on the pipeline while I get some attention.

XML artifacts are now served by pages

See merge request gitlab-org/gitlab!16790

As JSON is served via pages, XML should also be suitable

Protected branches log audits events

Closes #1487

See merge request gitlab-org/gitlab!16399

These changes add EE custom behavior for the different protected
branches (create, destroy and udpate).

It also adds a possible fix for
spec/services/git/branch_push_service_spec.rb that was using
expect_any_instance_of that was failing with the new EE modules

Reinitialize metrics files on webserver master start

See merge request gitlab-org/gitlab!16623

Docs only: Deprecation of Shibboleth SP

See merge request gitlab-org/gitlab!16587

The users should be directed toward the omniauth-saml
page instead since Shibboleth 3 supports SAML.

Move "Require code owner approval" setting from Project to ProtectedBranches

See merge request gitlab-org/gitlab!16187

I've set this up as a post-deploy background migration, taking advantage
of `each_batch` to set up jobs for Sidekiq workers to copy the project's
`merge_requests_require_code_owner_approval` to each of its protected
branch's `code_owner_approval_required` attribute. I've added some basic
tests here, as well.

I initially added a pair of #after_commit hooks to make sure projects
get updated while we were asynchronously chewing through the projects
and branches. However, I abandoned this, as a database reviewer supplied
a faster approach that shouldn't be an issue in terms of the total time
required to process the entities.

Fix console error when loading issues

See merge request gitlab-org/gitlab!16833

Fix outdated Polling development doc

See merge request gitlab-org/gitlab!16749

Also, add note about adding polling interval header

Removes information about docs in CE and EE

See merge request gitlab-org/gitlab!16883

Updated urls to point to gitlab-org/gitlab

Replace CE, EE text with GitLab

Removed references to CE and EE repos
and updated links to point to the new
GitLab project

Productivity Analytics: Project filter dropdown fixes

See merge request gitlab-org/gitlab!16814

- Increase number of projects to load to 50 and
excludes forks
- Pass groupId and projectId from dropdown to filter

Prevent unmodified designs from being versioned

See merge request gitlab-org/gitlab!16429

Add E2E test of pull mirroring with password auth

Closes gitlab-org/quality/testcases#119

See merge request gitlab-org/gitlab!16428

Create cluster dropdown component

See merge request gitlab-org/gitlab!16518

- Also rename EKS dropdown to cluster form dropdown

Remove eslint-plugin-html

See merge request gitlab-org/gitlab!16789

Remove self monitoring migration

See merge request gitlab-org/gitlab!16864

Docs: update CI/CD illustration

Closes #31693

See merge request gitlab-org/gitlab!16841

- Replace inforgraphic with typo
- Update version number

Simplify end-to-end test setup

See merge request gitlab-org/gitlab!16846

Besides that, this commit tries to fix an issue that happens on
staging, where user fabrication via API doesn't work, and it may
be due to the usage of let(:user) since other tests using
User.fabricate_via_api! don't use it in a let declaration.

In this commit I'm moving the user fabrication to the before block
and exposing it as an instance variable @user, so that it can be
used in the test itself.

Also, I have removed unnecessary steps that makes the test slower.