RMM: Build CUDA 12 packages

[bdice]

Description

This PR builds librmm and rmm conda packages using CUDA 12. Resolves #1207.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[bdice]

I'm looking at the CI output from the CUDA 12 C++ builds. We'll want to fix the ClobberWarnings like this one, perhaps by adopting rapids-core-dependencies which places the RAPIDS versions of CCCL libraries in a subdirectory instead of include/ or lib/ directly.

ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: nvidia/linux-64::cuda-cccl-12.1.55-0, file:///tmp/conda-bld-output/linux-64::librmm-23.04.00a-cuda12_230228_gfdad1308_47
  path: 'lib/cmake/cub/cub-config-version.cmake'

[jakirkham]

Following up on the cuda-python run_exports discussion, do we want this?

Edit: Ok punting on these if preferred

[bdice]

@jakirkham Should librmm have a run dependency on cuda-cudart-dev? I see the overlinking issues in librmm-tests, too (example).

WARNING (librmm-tests,bin/gtests/librmm/CUDA_ASYNC_MR_TEST): $RPATH/libcudart.so.12 not found in packages, sysroot(s) nor the missing_dso_whitelist.
.. is this binary repackaging?

We solved that issue in rmm in 865f707 by adding a host dep on cuda-cudart-dev (which used run_exports to get cuda-cudart into the run of rmm). However, I am not sure which is better:

1. Add cuda-cudart to librmm-tests run section (fix overlinking in librmm-tests only)
2. Add cuda-cudart-dev to librmm run section (all packages built with librmm will have a dependency on cuda-cudart-dev -- this is fine because librmm is header only and thus should only ever be in host unless used in another header-only package)

edit: I recall there may be an issue with run exports when used in this way... if I remember correctly, putting librmm in host won't allow its dependency cuda-cudart-dev to apply its run exports and put cuda-cudart into the package's run section?

[jakirkham]

Would suggest adding cuda-cudart-dev to host for librmm-test. Something like the snippet below may do the trick

[vyasr]

Hopefully the last review! I noticed a couple of things I missed before.

[vyasr]

Right, let's come back to this after we resolve the dfg work.

[vyasr]

Assuming CI passes, we look good to go! Awesome work @bdice!

[jakirkham]

/merge

[jakirkham]

Thanks all! 🙏