conda: strict channel priority + 'rapidsai' channel

[jameslamb]

Description

Strict channel priority was enabled by default RAPIDS-wide for rattler-build builds and conda environment creation in test jobs in #14

All of those use the rapidsai-nightly conda channel during most development.

I think that effort only covered the rapidsai-nightly channel (the one used by most CI during active development).

We should do a follow-up investigation and cleanup on the rapidsai channel (the one used by RAPIDS users and during releases).

Benefits of this work

• reduce the risk of conflicts in solves with strict channel priority
• reduces our storage footprint on anaconda.org

Acceptance Criteria

• rapidsai channel has been audited and 0 unnecessary packages remain

Approach

Determine a minimum RAPIDS version that should still be solvable and some testing criteria (see #14 for details).

@jameslamb 's quick glance at https://anaconda.org/channels/rapidsai suggests these might be good candidates to delete or move to the broken label:

• arrow-cpp (last updated May 31, 2022)
• arrow-cpp-proc (October 12, 2021)
• clang (May 23, 2019)
• clx (February 9, 2023)
• cupy (August 4, 2021)
• cusparselt (October 12, 2021)
• cutensor (October 12, 2021)
• datasharer (Mar 31, 2022)
• libclang (May 23, 2019)
• libclx (October 21, 2020)
• nccl (October 12, 2021)
• nvcc_linux-aarch64 (October 12, 2021)

Notes

N/A