[TASK] Use official NVTX wrappers rather than those from RAFT

[wphicks]

In discussion on #4445, it was pointed out that NVTX itself provides the same functionality that we currently use from RAFT for scoped NVTX range objects. It would be useful to standardize on this upstream tool for NVTX range objects.

[wphicks]

@cjnolet @jrhemstad @achirkin Opened this issue to track offline discussion that was begun around NVTX ranges. Assuming we do go this route, we should probably open similar issues in any other RAPIDS libraries that make use of these NVTX wrappers (or other custom wrappers) and then remove the custom version from RAFT.

[achirkin]

Would be nice if we managed to merge upstream the extra features from our implementation: vararg-formatted messages and randomly assigned visually distinctive colors.

[github-actions]

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

[github-actions]

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.