We need to manage some subtle caching edge cases. These are dealt with
by:

- Allowing clients to request a non-forgetful store
- Abstracting over throttling of actions per-period. A new method is
  introduced: `ExclusiveLease.throttle` that takes care of such needs.
- Allow specific keys to be forgotten after running policies
- Invalidating the `CurrentUserMode` cache for `admin_mode` if the
  session-bypass is active (which may change the value).

This deals with a very subtle cache collision problem. When this block
is run, it calls the users update-service, which computes, during
permission checks, the `admin` condition for this user. This is normally
fine, but this callback is executed _before_ the bypass-session admin ID
is set, which means that the cached value is stale during the execution
of the main action.

To avoid this, we deliberately discard the cached value of the `admin`
condition, leaving all other cache values intact.

Thankfully, `admin` is a cheap condition to recompute, and this does not
cause any additional I/O to be run.

Separately, the `Gitlab::Auth::CurrentUserMode` caches the value of
`admin_mode`, which may become invalidated due to the session-bypass
used for sessionless requests. We invalidate the cache when the
session-bypass setting is changed.
This invalidates the cached value for admin_mode, rather than requiring
the caller to know when to force recomputation.

A necessary change is made to prevent duplicate user-detail records.
See: https://gitlab.com/gitlab-org/gitlab/-/issues/333245

Changelog: fixed

Move lead and cycle time classes out from Group NS

See merge request gitlab-org/gitlab!63977

Relate Test Reports and Requirement Issues

See merge request gitlab-org/gitlab!63512

Update Gitaly version

See merge request gitlab-org/gitlab!64207

Update container scanning docs for Grype scanner

See merge request gitlab-org/gitlab!63707

Adjust Popover trigger on licence-check approvers panel

See merge request gitlab-org/gitlab!63782

Remove unused code for `no_matching_runner` failure reason

See merge request gitlab-org/gitlab!64002

Implement in-memory remotes for `update_remote_mirror` [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!63962

Update Plan pages with 14.0 Admin Area access info

See merge request gitlab-org/gitlab!64191

Docs improvement: Group Milestones API doesn't return subgroups' issues

See merge request gitlab-org/gitlab!64202

Move admin cohorts to separate controller

See merge request gitlab-org/gitlab!64015

Expand on Sidekiq data consistency docs

See merge request gitlab-org/gitlab!63028

Updated sidepanel in Dark mode [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!64182

Advanced Search Settings page does not load if the ES url is unreachable

See merge request gitlab-org/gitlab!63764

EE: true
Changelog: fixed

Fix DA dropdown alignment

See merge request gitlab-org/gitlab!64174

Hide preloaded token values while searching

See merge request gitlab-org/gitlab!64188

Add Ci::Minutes::AdditionalPack create API

See merge request gitlab-org/gitlab!63853

Add GraphQL subscriptions to frontend guidelines

See merge request gitlab-org/gitlab!64190

The `update_remote_mirror` functions is currently using on-disk remotes
by first calling `remote_mirror.ensure_remote!` followed by the call to
`update_repository`. Gitaly is phasing out support for on-disk remotes
though in favor of in-memory remotes, where the remote is specified as
part of the request itself.

Implement the ability to use in-memory remotes for this RPC. For now,
this is implemented behind a feature flag.

Show update branch message when MR branch diverged from target branch

See merge request gitlab-org/gitlab!64090

Update Gitaly version

See merge request gitlab-org/gitlab!64187

Add job-level keyword for DAST configuration

See merge request gitlab-org/gitlab!63370

Calculate mergeability check sync on first widget load

See merge request gitlab-org/gitlab!63506

Merge branch '332256-refactor-dropdowncontentscreateview-component-to-use-graphql-apollo' into 'master'

Refactor `DropdownContentsCreateView` component to use GraphQL + Apollo

See merge request gitlab-org/gitlab!63514

Roll-over issues from one iteration to another

See merge request gitlab-org/gitlab!62350

With release 14.0, Gitaly has introduced the ability to specify
in-memory remotes for the `UpdateRemoteMirror` RPC. We're about to start
using this new feature and thus need the new protobuf definitions which
include the new remote parameter.

Update the Gitaly Gem to 14.0.0.pre.rc2 to get the new definitions.

Update Admin Area text for Optimize doc

See merge request gitlab-org/gitlab!64130