Invalid CI container image

Summary

After the migration of the cms-gem-daq-project and its container registry under the cmsgemonline project, the container image used by the CI not longer exists. This prevents the CI jobs to succeed.

Steps to reproduce

Launch any CI pipeline
Observe a nearly immediate failure

What is the expected correct behavior?

The CI pipeline shouldn't fail because of a missing container image.

Possible fixes

Create and use a new custom container image for the CI.
Download the required packages inside the CI jobs.