Investigate bad_caston Mac OS 15 in Python tests

[ystade]

Description

#641 reveals a spurious bug that cannot be reproduced locally. This PR aims to find and fix the bug.

Checklist:

• The pull request only contains commits that are related to it.
• I have added appropriate tests and documentation.
• I have made sure that all CI jobs on GitHub pass.
• The pull request introduces no new warnings and follows the project's style guidelines.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.5%. Comparing base (4fa3fa3) to head (dfa8b39).
Report is 4 commits behind head on org-move.

❌ Your project status has failed because the head coverage (94.3%) is below the adjusted base coverage (96.1%). You can increase the head coverage or adjust the Removed Code Behavior.

Additional details and impacted files

@@            Coverage Diff             @@
##           org-move    #642     +/-   ##
==========================================
- Coverage      90.6%   90.5%   -0.1%     
==========================================
  Files           103     103             
  Lines         10670   10689     +19     
  Branches       1817    1817             
==========================================
+ Hits           9671    9680      +9     
- Misses          999    1009     +10     

Flag	Coverage Δ		*Carryforward flag
cpp	90.4% <100.0%> (+<0.1%)	⬆️	Carriedforward from a784c52
python	94.3% <ø> (-2.4%)	⬇️

*This pull request uses carry forward flags. Click here to find out more.

Files with missing lines	Coverage Δ
src/na/nasp/Solver.cpp	94.2% <100.0%> (+0.2%)	⬆️

... and 1 file with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[burgholzer]

dfa8b39 seems to have actually fixed the underlying problem.
I don't fully get why and how, but it definitely had to do with the fact that the minimums build would download mqt-core==3.0.0 which, eventually, would not pass the find_package(mqt-core 3.0.2 REQUIRED) call hidden in our FetchContent directive.
That leads to mqt-core==3.0.2 to be fetched and built into the wheel.
At the same time, mqt-core==3.0.0 is installed in the virtual environment and used when running the tests.
I am fairly sure that the problem arises from slightly different compilers used for compiling the two mqt-core libraries.
This has been resolved in #641 by introducing a new minimum version variable for the FetchContent call that allows 3.0.0 to be used.