Compiler errors in nvq++ should ask users to file an issue on cuda-quantum instead of llvm

[bmhowe23]

Required prerequisites

• Make sure you've read the documentation. Your issue may be addressed there.
• Search the issue tracker to verify that this hasn't already been reported. +1 or comment there if it has.
• If possible, make a PR with a failing test to give us a starting point to work on!

Describe the bug

As described in Issue #531, the error message that occurs when nvq++ crashes says PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace. In cuda-quantum cases, it would be much better to ask the user to report it to https://github.com/NVIDIA/cuda-quantum/issues/ instead.

Steps to reproduce the bug

As of commit 26fe7e7, see the steps provided in Issue #531.

Expected behavior

It would be much better to ask the user to report it to https://github.com/NVIDIA/cuda-quantum/issues/ instead, especially for __qpu__ functions, and perhaps for all nvq++ compiler crashes.

Is this a regression? If it is, put the last known working version (or commit) here.

Not a regression

Environment

• CUDA Quantum version: commit 26fe7e7 on main branch (latest as of the time of this issue)
• Python version: N/A
• C++ compiler: ghcr.io/nvidia/cuda-quantum-devdeps:ext-llvm-main
• Operating system: ghcr.io/nvidia/cuda-quantum-devdeps:ext-llvm-main

Suggestions

No response