Fix check-targets runtime library deps

[nanookclaw]

Summary

Closes #1571.

check-targets already depends on the global CUDAQ_RUNTIME_LIBS list, but a few runtime/plugin libraries used by target tests are not registered there. This adds an explicit guarded dependency list for the current targets that match the maintainer-provided missing-library list:

• cudaq-chemistry
• cudaq-platform-mqpu
• cudaq-py-utils
• cudaq-rest-qpu

The entries are wrapped in if(TARGET ...) so optional REST/Python/runtime plugin targets only become check-targets dependencies when that build actually defines them.

I did not add entries for cudaq-simulator-qpu or rest-remote-platform-client because I could not find current CMake targets or references with those names at HEAD; they appear to have been renamed or removed since the issue comment was written.

Testing

• git diff --check
• repo-wide CMake target/name search for the listed libraries

I did not run a full CUDA-Q build locally; this host does not have the project toolchain/CUDA build environment set up.

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[sacpis]

@Renaud-K @lmondada for viz.

[lmondada]

Thanks for the contribution!

I don't have the context to know what the expected behaviour of cmake should be here. @schweitzpgi can you check if this does what you want?

@nanookclaw just to confirm: this is not a unitary hack contribution, correct? If it is, you need to mark it as such today and we'd have to merge it in quickly. Otherwise let's resolve this next week.

[nanookclaw]

Correct, this is not a Unitary Hack contribution.

No urgency from that program on my side; resolving it next week is fine.