- When entering blocked URLs Gitea importer
  returns 500 error instead of a user friendly error
- Thic change fixes 500 error and adds more user
  friendly error indicating what went wrong

Merge branch 'update-secure-usage-ping-to-be-able-to-determine-number-of-jobs-by-user' into 'master'

Add distinct user count of secure stage items to usage ping

Closes gitlab-org/secure/general#63

See merge request gitlab-org/gitlab!26194

Ensure sidekiq-cluster emits JSON logs

See merge request gitlab-org/gitlab!26484

Remove presence validation of job title

See merge request gitlab-org/gitlab!26421

Add k3s provider

Closes #121679

See merge request gitlab-org/gitlab!24723

Add k3s specs
Remove unused k3s_hostname method
Remove :requires_admin tag from k8s spec
Always set allow local requests before and after

Merge branch '208718-transient-failure-for-spec-features-projects-wiki-user_updates_wiki_page_spec-rb-56-user' into 'master'

Wait for the 'Empty wiki' SVG to load before performing test assertions

Closes #208718

See merge request gitlab-org/gitlab!26309

Ensure more of Sidekiq logs are in JSON

Closes #208922

See merge request gitlab-org/gitlab!26480

- we want to capture the case of license failing for fallback

Sort Pipelines by ID on Project Import

See merge request gitlab-org/gitlab!26390

Explict check for non presence

Quarantine flaky SAML SSO Access spec

See merge request gitlab-org/gitlab!26435

No individual load needed in danger bot doc

See merge request gitlab-org/gitlab!26475

Update files when snippet is updated

See merge request gitlab-org/gitlab!23993

We can just re-use the Sidekiq JSON formatter to ensure this happens
since sidekiq-cli doesn't use the Sidekiq initializer.

Part of https://gitlab.com/gitlab-org/gitlab/issues/208922

Because the Sidekiq log formatter was initialized after Sidekiq
initialized Redis, we would see some unstructured logs emitted at boot.
To fix this, move the log formatter up earlier in the Sidekiq init
process.

Closes https://gitlab.com/gitlab-org/gitlab/issues/208922

- changelog needed for changes like this
- conditional not required

- split and rename effort was going on and missed it

- needed for collecting how many distinct users have triggered
  these items.

Vue Labels Select Dropdown

Closes #198431

See merge request gitlab-org/gitlab!24576

Updated richViewer for blobs

See merge request gitlab-org/gitlab!26260

Make design_management_versions.created_at not null

See merge request gitlab-org/gitlab!20182

Apply suggestion to db/migrate/20191114201118_make_created_at_not_null_in_design_management_versions.rb

- Previously when project was imported pipelines
  were shown in a reversed order
- This change sorts pipelines by id before doing
  the import to ensure that they are shown in a
  correct order on pipelines page

Remove required arguments from updateIssue mutation

See merge request gitlab-org/gitlab!26281

Add filepath redirect url for Release assets

See merge request gitlab-org/gitlab!25541

Part of https://gitlab.com/gitlab-org/gitlab/issues/27300

See merge request https://gitlab.com/gitlab-org/gitlab/-/merge_requests/25541

When the snippet content we need to replicate it
to the snippet repository.

Audit blocking user via API

See merge request gitlab-org/gitlab!25872

This maintains the idempotent nature of this API and consistent with
other state change method (e.g. `deactivated`).

Quarantine specs because of #208761

See merge request gitlab-org/gitlab!26373

Avoid using Timeout when deleting Sidekiq jobs

See merge request gitlab-org/gitlab!26392

Add trigram index on snippet description

See merge request gitlab-org/gitlab!26341

Reduce object allocation when using LogLimitedArray

See merge request gitlab-org/gitlab!26257

Make `warn` deprecation note a comment instead

See merge request gitlab-org/gitlab!26440

Fix incorrect class definitions

See merge request gitlab-org/gitlab!26218

Extend audit changes logic

See merge request gitlab-org/gitlab!26144

This extends `for_changes` method to accept reference of target object
being audited. Previously the `entity` is used to record both scope and
target change object. While that is true in some context (i.e. the
target model happens to be a User/Project/Group), it does not work for
`ApprovalProjectRule` (i.e. the target model is `ApprovalProjectRule`
and the entity is the associated Project)