Pyqrack

3 issues are addressed in this release:
1. `in_ket()` and `out_ket()` methods have been added to `QrackSimulator()`, for direct state vector writing and reading. We categorically discourage using these methods wherever avoidable, but automatic reactive Schmidt decomposition might still recover some separability from directly set state vectors.
2. Regression in `QPager` has been fixed, which previously prevented any paged simulations at all, above single OpenCL max allocation segment limits.
3. Per [the vm6502q/qrack README](https://github.com/vm6502q/qrack#qpager-distributed-simulation-options), `QRACK_QPAGER_DEVICES_HOST_POINTER` can specify a choice between OpenCL device memory or host memory, on a per-page basis.

With the use of `dump()` and `dump_ids()`, users can now directly output raw state vector amplitude values. (We discourage any recourse to state vector output unless one truly cannot operate without an explicit set of state vector amplitudes, or unless one would otherwise be compelled to reconstruct a state vector from measurement distributions.)

`dump_ids()` outputs the labels associated with state vector "wires" in permutation order. `dump()` outputs a list of complex number amplitudes, with corresponding "wire" order. These methods are not generally safe to use in threaded user code, (not including any internal Qrack threading). Also note that Qrack state vector amplitudes will typically have a randomized global phase offset, which is a matter of Qrack internal conventions and has no theoretically observable physical effect.

QEngine::ShuffleBuffers()` now relies on (semi-)async dispatch instead of `std::future` based threading. (This has been an aspirational goal, for several recent releases.)

SIMD based complex arithmetic has also been touched up, for performance.

Qrack has added internal decompositions for `mcmuln()` and `mcdivn()`, ("multiply-controlled multiplication/division modulo 'N'"). This might allow for better Schmidt decomposition.

Testing with a multi-platform build environment, (such as Intel HD integrated graphics + NVIDIA or AMD GPU,) I have achieved stable fully-entangled 32-bit `QPager` interoperability on an Alienware m17, as an example of a cross-platform OpenCL context. ("Platforms" limit OpenCL buffer sharing, among other aspects, and are often grouped by vendor.) In the process, multi-device and cross-platform interoperability are likely debugged and improved in general, such as while specifying a device list with the `QRACK_QPAGER_DEVICES` shell environment variable. [(See the Qrack README.)](https://github.com/vm6502q/qrack#qpager-distributed-simulation-options)