…ibility with CUDA 13. Fixes #693.

gpu_thrust.cuh: removed thrust::[unary|binary]_function which has been removed from CCCL.

* Simplify installation path configuration

Removed unnecessary path normalization and appending for installation.

* Updates CMake config for conditional installs

Modifies CMakeLists to conditionally build shared libraries and
install binaries only at the top-level project. Introduces the
INSTALL_BINARIES option to control the inclusion of example
binaries in the installation process. Corrects a typo from
'RATH' to 'RPATH' for build configurations.

* docs/cmake.md: fixed formatting of non-default options for mt and distribution

* cmake: wrapped user source install in if(INSTALL_BINARIES)

* docs/cmake.md: added INSTALL_BINARIES option

* gpu_thrust.cuh: modified initial thrust counting iterator declarations to use long long to avoid overflow at >30 qubits. Fixes #698.

* patched test of rightapplyCompMatr distributed validation

The operation validation tests previously always uses a statevector to test the "targeted amps fit in node" validation, though the rightapply*() functions cannot accept statevectors, instead only density matrices. Because the "was given a density matrix" validation happens before "targeted amps fit in node" validation, the latter intended triggered error was beaten out by the earlier unintended one.

Now, we are careful to pass a density matrix Qureg to the validation of "targeted amps fit in node" when triggered by a function which 'right-applies' (and is ergo only compatible with density matrices)

* changed literals to defensive type

---------

Co-authored-by: Tyson Jones <tyson.jones.input@gmail.com>

addresses #700

* Implement PauliStrSum random permutations inspired by [arXiv:1805.08385](https://arxiv.org/abs/1805.08385)

* Add randomisation to Trotter functions

* Document random Pauli permutations for Trotterisation

* Add test for Trotter randomisation

* Added unit tests requested by Quantum Motion

* tests/unit/trotterisation.cpp: updated time evo calls to new API

* tests/unit/trotterisation.cpp: updated authorlist

* Fixed valgrind errors

* tests/unit/trotterisation.cpp: tuned floating-point comparison epsilon to account for worst-case scenario which is single precision, single thread

* added get-arbitrary-qureg test util

since it will be used frequently by new input validation

* removed Qureg creation in validation tests

so that test failures do not cause memory leaks and e.g. add to valgrind noise. Tests now instead use getArbitraryCachedStatevec() or getArbitraryCachedDensmatr() to obtain an existing qureg with an arbitrary deployment.

* restoring missing-validation comments

since the validation for these functions wasn't added. Such functions have additional tests to their tested counterparts; for example, validating that matrix elements are non-zero when given a negative exponent

* fixing test category

* added missing operation validation tests

* fixed indentation

* making spacing consistent

and adding a missing Hermiticity validation to applyTrotterizedUnitaryTimeEvolution test

* added warning about untested deployments

* removed defunct signature

* patching C++ validation err msg

Previously, an error message of the C++ API was not substituting in values for its placeholder variables. This affected the C++ variants of the below functions when passing vectors for the targets and outcome parameters of mismatching length:
- calcProbOfMultiQubitOutcome
- leftapplyMultiQubitProjector
- rightapplyMultiQubitProjector
- applyMultiQubitProjector
- applyForcedMultiQubitMeasurement

* added missing C++ API signatures

* added C++-API validation tests

* updated doc warnings

* added Vasco to Trotter API authorlist

* merged Tyson's patches

---------

Co-authored-by: Tyson Jones <tyson.jones.input@gmail.com>
Co-authored-by: Maurice Jamieson <m.jamieson@epcc.ed.ac.uk>
Co-authored-by: Oliver Thomson Brown <otbrown@users.noreply.github.com>
Co-authored-by: Oliver Thomson Brown <8394906+otbrown@users.noreply.github.com>

CI updated to use latest AMD ROCm install instructions. As of this commit corresponding to ROCm 7.2.

---------

Co-authored-by: Oliver Thomson Brown <8394906+otbrown@users.noreply.github.com>

Remove numControls argument from applyMultiStateControlledSqrtSwap overloaded definition taking std::vector<int>

(cherry picked from commit 9c20792)

Co-authored-by: D-Exposito <dexposito@cesga.es>

* tests/unit/trotterisation.cpp: updated to use REQUIRE_AGREE and cached statevecs and densmats, and both permutePaulis options

* tests/utils/compare.hpp/cpp: added setters for test epsilon

* tests/unit/trotterisation.cpp: adjusted test epsilon for quad precision imaginary time evolution tests

* tests/unit/trotterisation.cpp: moved unitary time evo test to REQUIRE_AGREE

* tests/utils/cache.hpp/cpp: added additional utilities for creating and destroying temp caches (which I guess makes them not caches?) with a set number of qubits

* tests/unit/trotterisation.cpp: updated unitary time evo test to test across deployments

* tests/unit/trotterisation.cpp: reduced number of qubits and increased number of steps to admit the possibility of testing density matrices too

* tests/unit/trotterisation.cpp: added density matrix tests

* reduce test precision

to lazily pass CPU clang quad-precision

* skip Trotter tests in paid CI

* changing varname convention

* renaming cache funcs

---------

Co-authored-by: Oliver Thomson Brown <8394906+otbrown@users.noreply.github.com>
Co-authored-by: Tyson Jones <tyson.jones.input@gmail.com>

---------

Co-authored-by: Oliver Thomson Brown <otbrown@users.noreply.github.com>

Formerly, the Trotter functions (such as applyTrotterizedPauliStrSumGadget()), when passed permutePaulis=true, would randomly permutate the order of the passed PauliStrSum, mutating it and affecting the outputs of subsequent functions like reportPauliStrSum(). The function also contained superfluous memory allocs/copies equal in size to the PauliStrSum.

Now, the PauliStrSum is never mutated, and an internally allocated ordering list keeps track of the randomised permutation. We also updated the doc, renamed permutePaulis to permuteTerms, and improved validation. Note that 'permuteTerms' had not yet reached main/release, so these changes do not need to be documented in the v4.3 release notes.