…nces.

These changes add a new wrapper class to support interfacing between
kernels. Kernels on the device side have their own names and calling
conventions. Meanwhile, the C++ host code can capture references to
these kernels. The C++ compiler assumes it can erase the functions
completely and degenerate any reference to them as a pointer.
Furthermore, it may inline or wrap this code in a thicket of template
instantiations. But in order to be useful on the device side, the CUDA-Q
runtime must be able to determine which kernel was wrapped in C++ code,
lookup the device side code, and "link-time" optimize these calls, doing
calling convention conversions, etc. Furthermore, what must be done is
flavored by the execution environment.

Update the call paths of hybridLaunchKernel so that we can use the new
argument synthesis instead of falling back on and failing with quake
synthesis.

Add another deduction guide test (when using cudaq::sample). Mark all
tests that use deduction guides as C++ 20 (since C++ 17 doesn't have
guides).

Add a hacky workaround for python. Python needs to use the new argument
synthesis, but it is still using the old quake synthesis compiler pass.

Attempt to add split-file to installed stuff. [Doesn't work! Why not?]
Add guards to tests since some phases of the CI don't have the necessary
test utilities properly installed.

Mark failing state tests as UNSUPPORTED for now. These should be fixed
when the state handling using new argument synthesis is fully
implemented.

Fix bug when there are multiple callables.

synthesis to be used to get the expected error.

Reenable qvector_init_from_state.cpp. Hopefully this one was a red
herring chasing its own CI tail.

to fix the CI.