Unlike uploads that have been uploaded with Tempfile, the project
import/export archives are stored in a temporary cache directory and
remain there if:

1. Object storage is enabled
2. `move_to_store` is set to `true`.

CarrierWave will leave these files there until disk space runs out or a
clean step is run manually.

If `move_to_store` is set to `false`, CarrierWave will remove the files
after storing them. However, unlike a local file, with object storage,
the file is still copied, so setting `move_to_store` to `true`
doesn't buy us anything.

To ensure files are cleaned up, we can just inherit from the
GitlabUploader implementation of `move_to_store`, which returns `true`
if it's a local file, `false` otherwise.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60656

make the monitoring bundle reusable

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

Disable JIT Kubernetes resource creation for project level clusters

Closes #60500

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

Bump version of knative from 0.3 -> 0.5

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

Retry twice the system, API and unknown failures

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

Replace `No due date` with `None`

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

Better document the current states of our testing levels

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

Update README.md

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