8094 test reports

[poikilotherm]

What this PR does / why we need it:
After adding experimental JDK 17 build support, it would be nice to have a easier to read test report than filtering build log output. This PR aims to add them.

Which issue(s) this PR closes:

Relates to #8094

Special notes for your reviewer:
I edited a single Java file to trigger the build in a commit that would still be useful...

Suggestions on how to test this:
Take a look at the failing tests for JDK 17

Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Nope.

Is there a release notes update needed for this change?:
Nope.

Additional documentation:
None.

[coveralls]

Coverage increased (+0.002%) to 18.866% when pulling 29abfba on poikilotherm:8094-java17-exp-ci into 8b838f3 on IQSS:develop.

[poikilotherm]

Closing - there is no way a pull request from a forked repository is allowed to write a report.

See

• Resource not accessible by integration when using from fork PRs ScaCap/action-surefire-report#31 (comment)
• how to publish results from forked PRs? mikepenz/action-junit-report#97
• https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token

You can use the permissions key to add and remove read permissions for forked repositories, but typically you can't grant write access. The exception to this behavior is where an admin user has selected the Send write tokens to workflows from pull requests option in the GitHub Actions settings.

[poikilotherm]

It might be possible to work around this by uploading the test results (XML files) as a build artifact and process them with another workflow, using the new workflow_run event.

https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/