Replacing project references with container name in repository classes

See merge request gitlab-org/gitlab!23678

Close related GitLab issue on Sentry error resolve

See merge request gitlab-org/gitlab!23610

Update GitLab Packages

See merge request gitlab-org/gitlab!23706

Document the contexts we apply to workers

See merge request gitlab-org/gitlab!23995

Update usages of GlSprintf with dynamic message prop

See merge request gitlab-org/gitlab!24303

All git related classes (`Blob`, `Commit`, ...)
assume that `project` is the object that has the
repository. Nevertheless, now that we're adding
repositories to snippets, we need to abstract this.

We're moving from `project` to `container`.

Introduce 'license_scanning' CI vendored template"

See merge request gitlab-org/gitlab!22773

Fixes the commit description alignment in the last commit widget

See merge request gitlab-org/gitlab!23091

Vulnerable projects specs: fix descriptions

See merge request gitlab-org/gitlab!24236

New package details title base implementation

See merge request gitlab-org/gitlab!24055

Updated to match specs
Created new package_title component
Removed old title from package_app
Moved package tags into new title component
Created and updated tests
Created snapshot for title component

Update Maven documentation structure

See merge request gitlab-org/gitlab!23858

Created getting started section
Moved remote setup
Updated uploading
Created installation and removing

This adds the documentation on how to add context to cron-workers or
jobs scheduled in batch.

So we can go through them one by one to fix them

This disables the cops for current offences, so we can get to them
fixed 1 by 1.

This adds 2 cops for jobs scheduled that will likely miss context
information:

*CronWorkerContext*

Cron-Workers themselves run instance wide, so they aren't scoped to
users, namespaces, projects or other resources that should be added to
the context.

However, they often schedule other jobs that _do_ require context.

That is why the there needs to be an indication of context somewhere
in the worker. This can be done by using one of the following methods:

1. Wrap the code that schedules jobs in the `with_context` helper:

  def perform
    deletion_cutoff = Gitlab::CurrentSettings
                        .deletion_adjourned_period.days.ago.to_date
    projects = Project.with_route.with_namespace
                 .aimed_for_deletion(deletion_cutoff)

    projects.find_each(batch_size: 100).with_index do |project, index|
      delay = index * INTERVAL

      with_context(project: project) do
        AdjournedProjectDeletionWorker.perform_in(delay, project.id)
      end
    end
  end

2. Use the a batch scheduling method that provides context

  def schedule_projects_in_batch(projects)
    ProjectImportScheduleWorker.bulk_perform_async_with_contexts(
      projects,
      arguments_proc: -> (project) { project.id },
      context_proc: -> (project) { { project: project } }
    )
  end

*BulkPerformWithContext*

Often, when scheduling jobs in bulk, these jobs should have a separate
context rather than the overarching context.

If that is the case, `bulk_perform_async` can be replaced by the
`bulk_perform_async_with_context` helper, and instead of
`bulk_perform_in` use `bulk_perform_in_with_context`.

For example:

    ProjectImportScheduleWorker.bulk_perform_async_with_contexts(
      projects,
      arguments_proc: -> (project) { project.id },
      context_proc: -> (project) { { project: project } }
    )

Each object from the array in the first argument is yielded into 2
blocks:

The `arguments_proc` which needs to the return the list of arguments the
job needs to be scheduled with.

The `context_proc` which needs to return a hash with the context
information for the job.

When providing objects for a context, please make sure to load the
relevant relations. For routables (namespace, project), use
`.with_route`, for projects also include the namespace using
`.with_namespace`.

Refactor issue update service spec

Closes #198012

See merge request gitlab-org/gitlab!23663

Remove weekly update note

See merge request gitlab-org/gitlab!24073

Refactor docker container expiration policy form

See merge request gitlab-org/gitlab!24276

- generate select programmatically
- adjust tests
- separate fields from form

Switch between cloud providers in cluster creation screen

Closes #34802

See merge request gitlab-org/gitlab!23362

In the cluster creation UI, always display the
cloud provider links to allow the user to switch
between cloud providers.

Add warning that AWS HA install steps are under revision

See merge request gitlab-org/gitlab!24283

Improve container registry API docs

See merge request gitlab-org/gitlab!24178

Changed dependencies to reflect required array of strings

See merge request gitlab-org/gitlab!24230

Docs: add note on how to bypass overcommit

See merge request gitlab-org/gitlab!24304

De-quarantine AutoDevOps QA e2e test

Closes #198515 and #118481

See merge request gitlab-org/gitlab!24311

Replace set with let_it_be in EE specs (batch 2)

See merge request gitlab-org/gitlab!22990

Contributes to a removal of rspec-set gem

Admin mode in sidekiq jobs

Closes #35717

See merge request gitlab-org/gitlab!21792

Add client & server middlewares to support admin mode in Sidekiq jobs
Extend CurrentUserMode to enable setting admin user in RequestStore

Rename Storage::HashedProject to Storage::Hashed

See merge request gitlab-org/gitlab!24071

Step 1 - Fix `job_app` initialization and cleaning up of side-effects

See merge request gitlab-org/gitlab!23838

Use 'rules' in '.gitlab/ci/cache-repo.gitlab-ci.yml'

See merge request gitlab-org/gitlab!24306

Use 'rules' in '.gitlab/ci/cng.gitlab-ci.yml'

See merge request gitlab-org/gitlab!24308