Add a commutation aware rewriter/matcher and update quake-simplify to use

[taalexander]

Summary

This PR is based on #4984 and should only be merged after. The LoC should go down significantly as those dependencies go in. This PR actually cuts ~200LoC from quake simplify with the majority of the logic being the rewriter/matcher.

Adds a block-local commutation-aware rewrite driver and uses it in
quake-simplify to cancel inverse gates and fold rotations across operations
proven to commute.

For example, this tested MLIR:

%first = arith.constant 0.125 : f64
%second = arith.constant 0.625 : f64
%q = quake.null_wire
%rz0 = quake.rz (%first) %q
    : (f64, !quake.wire) -> !quake.wire
%s = quake.s %rz0 : (!quake.wire) -> !quake.wire
%rz1 = quake.rz (%second) %s
    : (f64, !quake.wire) -> !quake.wire
quake.sink %rz1 : !quake.wire

is simplified to the equivalent form:

%sum = arith.constant 0.75 : f64
%q = quake.null_wire
%s = quake.s %q : (!quake.wire) -> !quake.wire
%rz = quake.rz (%sum) %s
    : (f64, !quake.wire) -> !quake.wire
quake.sink %rz : !quake.wire

Applicable IR

The matcher operates on block-local, value-semantics Quake with linear scalar
!quake.wire controls and targets. Endpoints must implement
OperatorInterface and preserve wire threading.

Measurement and reset operations may be crossed only for supported scalar-wire
forms and only when commutation is proven. Reusable controls, references,
aggregates, fanout, block edges, calls or regions touching the wire, unsupported
quantum effects, and unresolved identities are commutation boundaries
and the analysis would need to be extended to support if required
(I haven't seen much oppurtunity in this right now).

Pipelines can canonicalize to this form with:

factor-quantum-alloc, memtoreg, linear-ctrl-form

This is backward compatible with existing quake-simplify use.

Benchmarking

On a set of internal benchmarks this shows about ~0-20% circuit improvements in total gate counts on individual benchmarks with a mean of 6.6% improvement across the total gate count in the sampled benchmarks. A bit less than I was hoping for but it's pretty clear where the low hanging fruit in the follow on work is.

[github-actions]

CI Summary (push) — ✅ passed

Run #31525733618 · ✅ 6 · ⏩ 7 · ❌ 0 · ⛔ 0

Top-level jobs (13)

Job	Result
binaries	⏩ skipped
build_and_test	✅ success
config_devdeps	✅ success
config_source_build	⏩ skipped
config_wheeldeps	✅ success
devdeps	✅ success
docker_image	⏩ skipped
gen_code_coverage	⏩ skipped
metadata	✅ success
python_metapackages	⏩ skipped
python_wheels	⏩ skipped
source_build	⏩ skipped
wheeldeps	✅ success

⏩ Skipped jobs (7) — intentionally skipped on PR builds; run on merge_group / workflow_dispatch

Job
binaries
config_source_build
docker_image
gen_code_coverage
python_metapackages
python_wheels
source_build

All sub-jobs (42) — every matrix leg, with links

Job	Status	Link
Build and test (amd64, gcc12, openmpi) / Dev environment (Debug)	✅ success	view
Build and test (amd64, gcc12, openmpi) / Dev environment (Python)	✅ success	view
Build and test (amd64, llvm, openmpi) / Dev environment (Debug)	✅ success	view
Build and test (amd64, llvm, openmpi) / Dev environment (Python)	✅ success	view
Build and test (arm64, llvm, openmpi) / Dev environment (Debug)	✅ success	view
Build and test (arm64, llvm, openmpi) / Dev environment (Python)	✅ success	view
CI Summary	❔ in_progress	view
Configure build (devdeps)	✅ success	view
Configure build (source_build)	⏩ skipped	view
Configure build (wheeldeps)	✅ success	view
Create CUDA Quantum installer	⏩ skipped	view
Create Docker images	⏩ skipped	view
Create Python metapackages	⏩ skipped	view
Create Python wheels	⏩ skipped	view
Gen code coverage	⏩ skipped	view
Load dependencies (amd64, gcc12) / Caching	✅ success	view
Load dependencies (amd64, gcc12) / Finalize	✅ success	view
Load dependencies (amd64, gcc12) / Metadata	✅ success	view
Load dependencies (amd64, llvm) / Caching	✅ success	view
Load dependencies (amd64, llvm) / Finalize	✅ success	view
Load dependencies (amd64, llvm) / Metadata	✅ success	view
Load dependencies (arm64, gcc12) / Caching	✅ success	view
Load dependencies (arm64, gcc12) / Finalize	✅ success	view
Load dependencies (arm64, gcc12) / Metadata	✅ success	view
Load dependencies (arm64, llvm) / Caching	✅ success	view
Load dependencies (arm64, llvm) / Finalize	✅ success	view
Load dependencies (arm64, llvm) / Metadata	✅ success	view
Load source build cache	⏩ skipped	view
Load wheel dependencies (amd64, 12.6) / Caching	✅ success	view
Load wheel dependencies (amd64, 12.6) / Finalize	✅ success	view
Load wheel dependencies (amd64, 12.6) / Metadata	✅ success	view
Load wheel dependencies (amd64, 13.0) / Caching	✅ success	view
Load wheel dependencies (amd64, 13.0) / Finalize	✅ success	view
Load wheel dependencies (amd64, 13.0) / Metadata	✅ success	view
Load wheel dependencies (arm64, 12.6) / Caching	✅ success	view
Load wheel dependencies (arm64, 12.6) / Finalize	✅ success	view
Load wheel dependencies (arm64, 12.6) / Metadata	✅ success	view
Load wheel dependencies (arm64, 13.0) / Caching	✅ success	view
Load wheel dependencies (arm64, 13.0) / Finalize	✅ success	view
Load wheel dependencies (arm64, 13.0) / Metadata	✅ success	view
Prepare cache clean-up	✅ success	view
Retrieve PR info	✅ success	view

✅ Required checks (6/6) — declared in .github/required-checks.yml for push

Required check	Status	Link
Build and test (amd64, llvm, openmpi) / Dev environment (Debug)	✅ success	view
Build and test (amd64, llvm, openmpi) / Dev environment (Python)	✅ success	view
Build and test (arm64, llvm, openmpi) / Dev environment (Debug)	✅ success	view
Build and test (arm64, llvm, openmpi) / Dev environment (Python)	✅ success	view
Build and test (amd64, gcc12, openmpi) / Dev environment (Debug)	✅ success	view
Build and test (amd64, gcc12, openmpi) / Dev environment (Python)	✅ success	view

[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.