✨ Migrate the IQM backend to configurable QDMI devices

[burgholzer]

🤖 AI text below 🤖

Summary

• export the stable iqm.default device ID and IQM symbol prefix through
  QDMI's public device-target helper so MQT Core can synthesize relocatable QDMI
  manifests
• expose the same metadata as Python package constants and preserve filesystem
  paths when registering the packaged library
• register the packaged IQM device only as a fallback and open a fresh device
  session for each IQMBackend
• preserve configured device defaults while applying explicit arguments and
  environment variables as session overrides
• keep scikit-build settings package-scoped when documentation builds the IQM
  package
• cover endpoint precedence, registration, metadata, and session behavior with
  hermetic tests

Motivation

This migrates QDMI-on-IQM from add_dynamic_device_library to the configurable
device registry and session APIs released in MQT Core 3.8.0. Applications can
use the stable device identity consistently across generated manifests,
configuration files, and Python integrations without duplicating loader
behavior.

The Python integration now consumes the published mqt-core~=3.8.0 package
directly. No source override, synthetic source version, or downstream LLVM/MLIR
setup is required.

Dependencies

• MQT Core 3.8.0 from PyPI
• merged QDMI commit b94be74fdac61dfdea51fc35ead5c314dbc89862

Validation

• Python 3.14 against the published MQT Core 3.8.0 wheel: 33 passed, 3
  credential-gated tests skipped
• full lint suite passed
• uv lock
• git diff --check
• the documentation environment replaced the former Git dependency with the
  published wheel; local notebook execution then reached the expected
  credential-gated live Resonance example
• no live IQM hardware tests were run

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!