Increase scan testing coverage
The regression monster is still too strong. All scans, tuning, and meta tuning should be tested, at least for API related regressions. This MR adds:
- Line-based coverage report to MRs (badly documented black magic, likely starts working when in development)
- Test overview page in pipelines (badly documented black magic, likely starts working when in development)
- Speed up software tests
- Testing of scan scripts with scan_parameters
- Testing for ITkPixV1 only scans
- Testing for tunings
- Testing for meta scans
- Testing is done using dual modules, to increase error surface
- Additional 2 software runner are added to stay < 1h testing time per push
- CI stages are defined, to allow early abort and combined coverage reports
- Bug fixes of scans, that turned out to be not working anymore
Edited by David-Leon Pohl