I've added a /lib/gitlab/issues/ module so now any usages of
Issues::Smth wihthin /lib/gitlab/issues/* will look for Smth
within /lib/gitlab/issues folder, so we need to change those
usages to resolve to the external definitions outside of
/lib/gitlab/

Rebalancing issues in a long running transaction with a lock
retry generates subtransactions that lead to overall DB
performance degradations.

see https://gitlab.com/gitlab-org/gitlab/-/issues/338346

So we are moving issues rebalancing out of one single big
transaction by locking the repositioning within a project or
namespace during the rebalance.

Rebalancing is a long running job, it can take multiple hours
to finish a rebalance of a namespace with large number of issues.
This change introduces a simple mechanism of resuming rebalance
from a checkpoint.

- A limited number of rebalancing jobs are allowed to run,
5 at this point
- Before starting a rebalance the number of running rebalances
is checked.
- If the limit of running rebalances is met we store the first
project id from the list of projects to be rebalanced, use that
to determine how many rebalances are running
- We load all namespace issue ids into a redis sorted set, by
using current issue relative position as a score. We do that so
that we do not have to run a very slow SQL query that would require
otherwise ordering and we are able to load the issue ids in batches
and get the sorting for free from redis. This also allows us to
pick up issue loading in case of a failure from the project we
read last time
- Because we are no longer in a DB transaction and we want to
preserve the relative position of the issues after the rebalance
we need to disable issue repositioning in the namespace
while rebalancing.
- Once all the issue ids are loaded the positions are being
updated in batches by reading the issues in a sorted order and
computing the new positions based on number of issues in the
namespace, distributed equally.
- Every successfull update stores a checkpoint from which the
next update can be picked-up in case of a failure
- Updates are retried on failure and batch sizes are dynamically
downsized and retried down to a limit of 5 issues per batch.
- All cache keys are set to expire in 10 days from last interaction
to leave enough time for the job to be picked up and also cleanup
any unused keys after given grace period.

Changelog: changed

Remove unused ActiveRecord Scope with_project_and_namespace

See merge request gitlab-org/gitlab!70213

Allow to save and apply inherited templates on service desk issues

See merge request gitlab-org/gitlab!67786

Upgrade fog-aws to v3.12.0

See merge request gitlab-org/gitlab!68969

Merge branch '338006-fix-release-features-tables-cross-joining-ci_builds-environments-dashboards-environment' into 'master'

Resolve Environment dashboard features cross joining with CI DB

See merge request gitlab-org/gitlab!68870

Move the Omnibus update doc to the GitLab repo

See merge request gitlab-org/gitlab!70281

Show disabled input for Service Desk custom email

See merge request gitlab-org/gitlab!69857

Open reply box on resolved design discussions

See merge request gitlab-org/gitlab!70359

[4/5] Add unauthenticated API throttle settings to admin area

See merge request gitlab-org/gitlab!69486

tags: Always enable fix for verification of long tag messages

See merge request gitlab-org/gitlab!70051

Set `job_token_scope_enabled` to false by default

See merge request gitlab-org/gitlab!69502

Users are confused about the `service_desk_email` configuration and
often wonder why it's not working correctly even when it's configured.

Changelog: changed

Fix a bug where reply box does not open on
resolved design discussions.

Changelog: fixed

Merge branch '338069-address-the-primary-key-overflow-risk-for-the-ci_build_trace_chunks-table-step-3-drop' into 'master'

Resolve "Address the Primary Key Overflow risk for the ci_build_trace_chunks table - Step 3: Drop temporary columns and triggers"

See merge request gitlab-org/gitlab!69632

Update dependency @gitlab/ui to v32.10.1

See merge request gitlab-org/gitlab!70349

Add upvotes to merge requests documents

See merge request gitlab-org/gitlab!66671

Enable canary switching during spec execution

See merge request gitlab-org/gitlab!69421

Add requires_admin tag to index tests

See merge request gitlab-org/gitlab!70316

Update container policy screenshot

See merge request gitlab-org/gitlab!70241

Remove subtransactions from partition management

See merge request gitlab-org/gitlab!70231

Refactor admin PAT creation for LDAP scenarios

See merge request gitlab-org/gitlab!70038

Update Gitaly version

See merge request gitlab-org/gitlab!70347

Enable surfacing false positives for vulnerabilities

See merge request gitlab-org/gitlab!69700

Consolidate the use of IDs in board state [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!69733

Disable touching individual DB migration files in production

See merge request gitlab-org/gitlab!70204

Disable method instrumentation initialization [RUN ALL RSPEC] [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!69662

Set different session cookie for Geo secondaries

See merge request gitlab-org/gitlab!69759

Add Praefect log location

See merge request gitlab-org/gitlab!69600

Update NameID format recommendation

See merge request gitlab-org/gitlab!70324

Remove `Graphql/Description` from `.rubocop_manual_todo.yml`

See merge request gitlab-org/gitlab!69826