[FEA] pylibcugraph error handling should include detailed error message from the C API

[rlratzel]

pylibcugraph APIs use a utility to check for success after calling C APIs, but do not extract the detailed error message available. Having additional details would be very helpful in debugging problems, such as the one reported here.

There's already a FIXME to address this here.

cc @ChuckHastings

---

For Developers below this line

• [] Code passes CI
• [] Code in pylibcugraph Python layer
• [] Test cases at each layer (for MG tests, a note in the PR description indicating the new/existing MG tests were run and passed)