chore: Use pull-through cache for CI container images

[aledegano]

Create and use specific values file for SDSC Renkulab CI-deployments.

/deploy

[RenkuBot]

You can access the deployment of this PR at https://ci-renku-4486.dev.renku.ch

[leafty]

Do we need to redefine these?

[aledegano]

The default is false and we do not set this flag anywhere else, although it's needed for some of the CI tests.
So as it stand yes we need it, perhaps we could make true the default but I don't know which ramifications that might have outside of our deployments...

[leafty]

and for gitlab.enabled=false? I thought it was already set to false by default.

[aledegano]

I've removed that key and internalGitlab as well.

[leafty]

IMPORTANT NOTICE: this will break CI deployments on all component repositories.

The component repositories will need to use the new values file.

[olevski]

Why do we need a separate minimal values file now?

[leafty]

IMPORTANT NOTICE: this will break CI deployments on all component repositories.

See:

    steps:
      - name: Checkout renku repository
        uses: actions/checkout@v4
        with:
          repository: SwissDataScienceCenter/renku
          sparse-checkout: |
            minimal-deployment

The sparse-checkout argument will need to be updated in all component repositories.

🤔 Wait... This should still work, though the CI/CD should be updated.

[RenkuBot]

Tearing down the temporary RenkuLab deployment for this PR.