🐛 Fix test suite regression in heuristic mapper

[burgholzer]

Description

Due to some unknown reason, the test suite suddenly started to fail on linux systems for one particular heuristic mapper test.
The underlying issue seems to have been some concurrency issue in combination with the logging functionality in the heuristic mapper.
The fix for now was to add a random suffix to the data logger path for all respective tests.

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.4%. Comparing base (dd85dd0) to head (1ca32b8).
Report is 148 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##            main    #559     +/-   ##
=======================================
- Coverage   90.4%   90.4%   -0.1%     
=======================================
  Files         87      87             
  Lines      10052   10052             
  Branches    1722    1722             
=======================================
- Hits        9093    9092      -1     
- Misses       959     960      +1     

Flag	Coverage Δ		*Carryforward flag
cpp	90.1% <ø> (-0.1%)	⬇️
python	95.9% <ø> (ø)		Carriedforward from b9621fb

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

see 1 file with indirect coverage changes

[burgholzer]

This was really getting frustrating.
And it was not reproducible on macOS at all.
Due to lack of time, this PR simply drops the one problematic test.
The underlying cause is related to concurrency and how the tests are being run.
However, I it has proven to be quite hard to really find out what is going on.
Assuming CI passes, this should be good enough for now.

[burgholzer]

Alright, after some more trial and error it turns out that the error can also be fixed by adding a random suffix to the data logger path, which seems to avoid the concurrency problems.
All tests are green again now ✅