WIP: switch from 'cuda-python' to specific components (e.g. 'cuda-bindings')

[jameslamb]

Description

Contributes to rapidsai/build-planning#285

cuda-python is a metapackage and sometimes pulls in components that RAPIDS libraries don't need. This PR is part of a series dropping direct use of cuda-python in favor of depending only on those specific components.

• drops dependency on cuda-python
• adds explicit dependencies on components:
  • cuda-bindings >=12.9.2,<13.0 (CUDA 12), cuda-bindings >=13.0.1,<14.0 (CUDA 13)
• adds explicit testing of oldest cuda-bindings in CI

Notes for Reviewers

🚧 not ready for review, just opening to get feedback from CI 🚧

Why these specific bounds?

• these roughly match what we were getting with cuda-python
• worked through finding compatible ranges in [NOT READY FOR REVIEW] WIP: switch from 'cuda-python' to specific components (e.g. 'cuda-bindings') rmm#2460 (comment)
• cuda-bindings major version follows the CTK major version, so kept a ceiling just like we currently have for cuda-python

This PR has dependencies

• WIP: switch from 'cuda-python' to specific components (e.g. 'cuda-bindings') NVIDIA/raft#3068
• [NOT READY FOR REVIEW] WIP: switch from 'cuda-python' to specific components (e.g. 'cuda-bindings') rmm#2460

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.