* Add row to configuration page for corpus management

Remove confusing messaging from example deprecation template file

See merge request gitlab-org/gitlab!70232

Update style of allow_failure keyword reference

See merge request gitlab-org/gitlab!70043

Add steps how to add emails to profile

See merge request gitlab-org/gitlab!69911

Add instructions to add email to user as admin

See merge request gitlab-org/gitlab!69913

Enable the `infinitely_collapsible_sections` feature flag on

See merge request gitlab-org/gitlab!70198

GraphQL for dependency proxy TTL policy

See merge request gitlab-org/gitlab!68900

Remove callbacks on secondary emails

See merge request gitlab-org/gitlab!69167

The 3 User "secondary emails each have default behavior. Previously
this behavior was managed through a complex set of model callbacks that
required workarounds to have the correct behavior. That complexity
fostered multiple security issues. We have refactored the default
behavior to exist only in custom getter methods, so there is no more
need to use callbacks to manipulate the database values. This removes
the callbacks, because they no longer have any effect.

Add connected agents to cluster agents GraphQL response

See merge request gitlab-org/gitlab!69820

Pull Zuora plan ID from CustomersDot API

See merge request gitlab-org/gitlab!69520

Merge branch '329053-ruby-saml-security-update-breaks-handling-of-large-saml-responses' into 'master'

Introduce max saml message size setting

See merge request gitlab-org/gitlab!69647

Move slash commands screenshot

See merge request gitlab-org/gitlab!70174

Merge branch '340481-follow-up-from-fix-style-and-language-issues-in-elasticsearch-page' into 'master'

Edit and re-write Elasticsearch page content

See merge request gitlab-org/gitlab!69971

Fix not being able to delete unparseable policies

See merge request gitlab-org/gitlab!70114

Add foundation for JH phone verification codes except db

See merge request gitlab-org/gitlab!69526

Fix editing network policies without policy management project

See merge request gitlab-org/gitlab!70171

Docs: Remove mention of rails env changing logs

See merge request gitlab-org/gitlab!70019

Enable sidekiq job limits by default through application configuration

See merge request gitlab-org/gitlab!68982

Add schedules info to the saved scans list

See merge request gitlab-org/gitlab!69895

Fix loading performance of policies list

See merge request gitlab-org/gitlab!69916

Fetch notes along discussions using GraphQL

See merge request gitlab-org/gitlab!69353

This allows configuring Sidekiq job limits from the admin area, or
using the API.

Configuration options are:

**Limiter mode***

`sidekiq_job_limiter_mode`, this can either be `track` (0), or
`compress` (1).

In `track` mode, this will only report errors when the arguments for
jobs exceed the `sidekiq_job_limiter_limit_bytes` option. But no jobs
will be compressed or rejected.

In `compress` mode, the jobs will be compressed before they are stored
in Redis. If a job's arguments would still exceed
`sidekiq_job_limiter_limit_bytes` after compression an exception would
be raised and the job would not be stored in Redis. Setting the
`sidekiq_job_limit_bytes` to 0 avoids raising an error.

Jobs will get compressed or rejected when they are scheduled.

Default is `compress`.

**Compression threshold bytes**

When the job's arguments exceed this size, the job's arguments will be
compressed before storing them in Redis. Below this size, nothing will
happen.

Default is 100Kb.

**Size limit**

When jobs exceed this size after compression, an exception will be
raised preventing the jobs from being stored in redis.

Default is 0 bytes.

The defaults will enable job-compression without limiting for
self-managed installations. Compression has been running on
GitLab.com. On GitLab.com we're rejecting jobs exceeding 5MB after
compression.

The validation is entirely skipped for BackgroundMigrations, since the
scheduling of those cannot depend on the state of the schema. So we
cannot load the settings into memory to run the clientside
validation.

Changelog: added

Updates the helm [documentation](https://docs.gitlab.com/ee/user/packages/helm_repository/) with:
* Properly document the `<channel>` parameter.
* Document that URL-encoded project ID can be used and when.
   * That's issue https://gitlab.com/gitlab-org/gitlab/-/issues/340041
* Document that when using the deploy tokens, the related username must be used for authentication.

Add endpoints to query and update
dependency proxy image ttl group policies

Changelog: added

Remove outdated GitLab version refs from doc pages

See merge request gitlab-org/gitlab!70091

Add Ci::StuckBuilds::DropService to hold logic needed for use in StuckCiJobsWorker

See merge request gitlab-org/gitlab!69564

Revise messages about creating follow-up issue

See merge request gitlab-org/gitlab!70070

Migration to finalize swap of bigint ci_builds.id

See merge request gitlab-org/gitlab!65201

Retry CI trace archive if left in incomplete state

See merge request gitlab-org/gitlab!68906