Fix Sonar in CI to get coverage back

[Hartorn]

Description

Related Issue

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Checklist

• I've read the CODE_OF_CONDUCT.md document.
• I've read the CONTRIBUTING.md guide.
• I've updated the code style using make codestyle.
• I've written tests for all new methods and classes that I created.
• I've written the docstring in Google format for all the methods and classes that I used.

[mattbit]

@Hartorn

Last analysis has warnings
The following error(s) occurred while trying to import coverage report:
Invalid directory path in 'source' element: /home/runner/work/giskard/giskard/giskard
Cannot resolve 149 file paths, ignoring coverage measures for those files
Cannot resolve the file path 'init.py' of the coverage report, the file does not exist in all 'source'.

[mattbit]

I think modifications of suite.py were erroneously included.

[mattbit]

Why this is here?

[Hartorn]

I think it's because of main was updated with some stuff, I get some conflict

[Hartorn]

@mattbit did you get notified before with PR was not in draft anymore ? or did you saw it in pull requests ?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information