`nvq++` does not respect user's choice for output object filename

[boschmitt]

Required prerequisites

• [X] Consult the security policy. If reporting a security vulnerability, do not report the bug using this form. Use the process described in the policy to report the issue.
• [X] Make sure you've read the documentation. Your issue may be addressed there.
• [X] 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

When compile object files using nvq++, the driver does not honors the filename provided by the user.

Steps to reproduce the bug

Try compiling an object file using nvq++:

nvq++ -c foo.cpp -o my_file.o

The output will be an object file named foo.o instead of my_file.o

Expected behavior

nvq++ should generate an object file with name my_file.o

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

Not a regression

Environment

• CUDA Quantum version: nvq++ Version proto-0.8.0 (https://github.com/NVIDIA/cuda-quantum 6016e2f23216b64f0fca083bef22fb8266ea9049)
• C++ compiler: c++ (GCC) 13.2.1 20240316 (Red Hat 13.2.1-7)
• Operating system: Linux fedora 6.8.9-200.fc39.x86_64

Suggestions

No response