Refactor QDMI device architecture: Remove static device libraries

[coderabbitai]

Background

The current QDMI device implementation includes both static and dynamic versions of device libraries. This dual approach adds complexity to the build system and maintenance overhead.

Goal

Revisit the architecture and evaluate whether we can transition to building all QDMI device libraries as shared libraries by default, removing the need for static library variants.

Questions to Address

• What are the advantages of the current static library approach?
• Can we standardize on shared libraries across all platforms?
• What are the implications for different platforms (especially Windows)?
• How does this affect the consumption of external QDMI devices?

Context

This issue was raised during discussion in PR #1328:

• PR: ✨ New QDMI Device to represent SC Devices #1328
• Comment: ✨ New QDMI Device to represent SC Devices #1328 (comment)
• Requested by: @ystade

Notes

This refactoring should be addressed after implementing Windows support for dynamic library loading (see related issue).