✨ QDMI support

[burgholzer]

What's the problem this feature will solve?

QDMI, which is available at https://github.com/Munich-Quantum-Software-Stack/QDMI, provides a standardised interface for querying and controlling quantum devices.
It forms a central part of the Munich Quantum Software Stack (MQSS).
Given mqt-core's central role in the MQT, it seems a suitable place to maintain the MQT's QDMI integration/compatibility.

QDMI should, eventually, make all the various architecture representations currently employed across the MQT obsolete and unify them behind a common interface.
As a nice bonus, this directly allows us to hook in execution of circuits for the backends that we have access to.

Describe the solution you'd like

mqt-core should add another new module encapsulating all the functionality related to QDMI.
This includes

• a FoMaC library to abstract from the low level interface, drawing inspiration from https://github.com/Munich-Quantum-Software-Stack/QDMI/tree/develop/examples/fomac.
• a driver implementation for loading device implementations
• a couple of commonly used device implementations throughout the MQT; especially, mqt-qmap and mqt-bench
• high-level Python bindings to use the QDMI devices from Python, drawing inspiration from https://github.com/cda-tum/mqt-bench/blob/main/src/mqt/bench/devices/device.py

The most interesting part in all of this is probably the driver and how it interacts with the Python bindings. Some of the device implementations provided as part of this effort could probably be statically linked and, hence, would be directly accessible. However, it might also be interesting to allow loading of arbitrary QDMI device implementations provided as shared libraries.