[BUG]: Update cuGraph to always explicitly specify RMM pool size and avoid using rmm::detail APIs

[harrism]

rapidsai/rmm#1417 and followon PRs make a number of improvements and changes to help consumers of RMM avoid accessing RMM's detail namespace.

initial pool size in pool_memory_resource is required to be provided (no longer optional)
rmm::detail::available_device_memory() (moving to `rmm::available_device_memory())
Move alignment utility functions out of detail namespace.
Add utility to calculate an aligned percentage of free device memory in bytes. This way, existing instantiations of pool_memory_resource(upstream) can be replaced by pool_memory_resource(upstream, rmm::percent_of_free_device_memory(50), which matches previous behavior.

cuGraph should be updated for these changes once rapidsai/rmm#1417 is merged. I have a PR ready to open.

Version

24.02

Which installation method(s) does this occur on?

Source

Describe the bug.

cuGraph calls RMM detail APIs, namely this one, which is going away (it's becoming a public API, but still this is a great example of what not to do).

cugraph/cpp/include/cugraph/mtmg/resource_manager.hpp

Line 109 in d7c88d1

auto const [free, total] = rmm::detail::available_device_memory();

Minimum reproducible example

No response

Relevant log output

No response

Environment details

No response

Other/Misc.

No response

Code of Conduct

• I agree to follow cuGraph's Code of Conduct
• I have searched the open bugs and have found no duplicates for this bug report