Add action to publish test results in the PR

[ThomasCluzel]

Proposed changes

Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.

This PR adds a feature to the CI workflow that publish tests results as a comment of the pull request that is updated each time a new CI workflow is run.

Types of changes

What types of changes does your code introduce to this project?

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I agree with the CODE OF CONDUCT
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[github-actions]

Results of the CI pipeline

5308f25b3ff413b904dcb6e575d96e7b579cd2c4a11309399d22f103ec7dd914
82de23ceb6e9a9ffd37db090c74288ded047d979870f200bd6abcba3922e95e3
Launching test tests/fortran.bash...success
Launching test tests/import_pylint_results.bash...success
Launching test tests/java.bash...success
Launching test tests/pylint.bash...success
Launching test tests/python.bash...success
Launching test tests/shell.bash...success
Launching test tests/shellcheck.bash...success
[INFO] Test CNES sonar-scanner: 0 tests failed out of 7