[FEA] Decouple this project from rapidsai/ci-imgs

[jameslamb]

Is your feature request related to a problem? Please describe.

Today, this project relies directly on the images built from https://github.com/rapidsai/ci-imgs

https://github.com/rapidsai/docker/blob/f49af7baf2adb3cb20b748e4fcee3b45e2edaa6a/Dockerfile#L18

That has been convenient (for example, ci-imgs takes care of everything related to supporting new CUDA versions), but the tight coupling creates some development friction in both projects.

For example, see #831 for a description of how a "make images faster to pull in CI" change in ci-imgs resulted in a release blocker here in this repo.

Describe the solution you'd like

Nothing in this repo should depend on base images from rapidsai/ci-imgs.

Describe alternatives you've considered

N/A

Additional context

Changing base images is risky because it introduces possible changes in user-facing details like permissions, user IDs, etc.

I'd approach it like this:

1. inline everything from the Dockerfiles in into this repo with minimal changes https://github.com/rapidsai/ci-imgs
   • [x] factor out rapidsai/ci-conda (#834)
   • [x] factor out rapidsai/miniforge-cuda (#836)
2. expand the container-canary checks in https://github.com/rapidsai/docker/tree/main/tests/container-canary to cover as much as we think is relevant
   • [x] expand container-canary checks (#839)
3. update Dockerfile here with optimizations specific to these images (for example, RAPIDS users probably do not need the gha-tools tools)
   • [x] remove rockylinux-specific stuff (#839)
   • [ ] move repetitive code into shared scripts (#840)