Added IP restriction docs to groups

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

Revert concurrent pipeline creation for pipeline schedules

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

Add docs for Application Development Platform

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

Add Create Deep Dives to development docs

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

#57815 Changes for UltraAuth users

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

Disabled password authentication for the users registered using
omniauth-ultraauth strategy

Update dependency @gitlab/ui to ^4.3.0

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

See https://gitlab.com/gitlab-org/create-stage/issues/1 for more context

Use new Code Quality job definition in Auto DevOps

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

Look for new branches more carefully

Closes #59257

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

This commit reverts the previously introduced concurrent pipeline
schedule creation which was a viable solution for mitigating
inconsistent pipeline schedule by Sidekiq Memory Killer.

Rename TOKEN_TYPES to USER_TOKEN_TYPES

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

Move some quick actions feature specs to unit tests

Closes #60515

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

Move some feature specs for issues/merge requests quick actions
to unit tests. They are taking too long to run on the pipelines.

Backport approval MR rules report_type migration to CE

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

Add migrations needed to encrypt feature flags client tokens

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

Feature flag default on catfile cache

Closes gitaly#1712

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

Https many links in docs

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

Update list items to conform to documentation style guide

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

In certain cases, GitLab can miss a PostReceive invocation the first
time a branch is pushed. When this happens, the "branch created" hooks
are not run, which means various features don't work until the branch
is deleted and pushed again.

This MR changes the `Git::BranchPushService` so it checks the cache of
existing branches in addition to the `oldrev` reported for the branch.
If the branch name isn't in the cache, chances are we haven't run the
service yet (it's what refreshes the cache), so we can go ahead and
run it, even through `oldrev` is set.

If the cache has been cleared by some other means in the meantime, then
we'll still fail to run the hooks when we should. Fixing that in the
general case is a larger problem, and we'd need to devote significant
engineering effort to it.

There's a chance that we'll run the relevant hooks *multiple times*
with this change, if there's a race between the branch being created,
and the `PostReceive` worker being run multiple times, but this can
already happen, since Sidekiq is "at-least-once" execution of jobs. So,
this should be safe.

Remove deprecated group routes

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

Upgrade Gitaly to v1.47.0

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

Fix typos, grammar and wording for SAST and DS report JSON docs

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

The feature flag has been introduced an was turned off by default,
now the it will default to be turned on. That change would still allow
users to turn this feature off by leveraging the Rails console by
running:

`Feature.disable("gitaly_catfile-cache")`

Another option is to manage the number of items the LRU cache will
contain, by updating the `config.toml` for Gitaly. This would be the
`catfile_cache_size`:
https://gitlab.com/gitlab-org/gitaly/blob/0dcb5c579e63754f557aef91a4fa7a00e5b8b127/config.toml.example#L27

Closes: https://gitlab.com/gitlab-org/gitaly/issues/1712