[FEA] Support memory resources from CCCL 3.2

[bdice]

Is your feature request related to a problem? Please describe.
Recently, RAPIDS/CCCL nightlies began failing due to a change in CCCL's memory resources. See NVIDIA/cccl#5313

Describe the solution you'd like
RMM should support CCCL’s new memory resources, which are targeting CCCL 3.2. RAPIDS is currently using CCCL 3.1.

[bdice]

Current plan for adoption:

Allocation Interfaces

This list of tasks requires CCCL 3.1+, so we can ship these changes in 25.12.

1. Build RMM w/ 3.1 via polyfill and allocate updates (Support building with CCCL 3.1.0 #2017) (25.10)

• Need to verify that all of RAPIDS builds with CCCL 3.1 with these changes in RMM, and ask Spark to do testing with the same pre-release of CCCL 3.1. The goal is to unblock adoption of CCCL 3.1 for RAPIDS.
• Then hopefully CCCL+RAPIDS CI should work.

2. Update polyfill to new allocate signature (RMM internal refactoring) Use CCCL MR interface internally #2112 (25.12)
3. Refactor RAPIDS to use new allocate signature Migrate RAPIDS to CCCL MR interface (new allocation APIs) #2126 (25.12)
4. Deprecate old allocate signature Add deprecation warnings for legacy MR interface #2128 (25.12)
5. Remove deprecated legacy allocate interfaces Remove legacy memory resource interface in favor of CCCL interface #2150 (26.02)

Memory Resource Handling

This list of tasks requires CCCL 3.2+, so we will need to work on that migration in 26.02.

• Implement a bridge for pointer-based resources CCCL 3.2 resource ref compatibility #2176, [FEA] Implement a bridge to help migrate away from device_memory_resource* #2143 (26.02)
• Upgrade RAPIDS to use CCCL 3.2. Update to CCCL 3.2 build-planning#237, Update to CCCL v3.2.0 rapids-cmake#955 (26.02)
• Adopt any_resource in device-resource global mapping Store any_resource in device-resource global mapping #2200 (26.02)
• Adopt any_resource in custom containers Store any_resource in device_buffer and device_uvector #2201 (26.02)
  • Containers storing RMM resource_refs should instead store cuda::mr::any_resource
• Deprecate pointer-based resources (26.04)
  • Refactor logging_resource_adaptor to shared CCCL MR design #2246
    • This design will replace Fix adaptor lifetime issues by storing any_resource #2208
    • This design will replace Use resource refs in Cython #2209 temporarily -- we'll still want to refactor the Cython layer afterward
  • Deprecate pointer-based per-device resource APIs #2210
  • Deprecate set_current_device_resource pointer-based API cudf#21018
  • Store any_resource in device_uvector_policy raft#2917
  • Update RMM memory resource APIs to ref-based equivalents raft#2920
  • Adopt any_resource in BufferResource and RmmResourceAdaptor rapidsmpf#772
  • Update RMM memory resource APIs to use ref-based equivalents cuml#7668
  • Update RMM memory resource APIs to ref-based equivalents cugraph#5392
• Remove RAPIDS usage of pointer-based resources (26.04)
• Remove internal usage of pointer-based resources (remaining work of [FEA] Implement a bridge to help migrate away from device_memory_resource* #2143)

[bdice]

CCCL 3.1.0 + RAPIDS 25.10 CI is working, and RAPIDS is nearly ready to adopt the new CCCL version in 25.12. This will complete task (1) above.