Finish and promote open-test-reporting format

[marcphilipp]

The Open Test Reporting format was introduced to replace the legacy XML format for test results in a way that supports all features of JUnit 5. It's designed to alleviate users from the mental load of having to translate from the logical structure of their test cases to an outdated technical format and vice versa. This task adds the missing pieces to make it truly useful and superior to the old format. This will reduce friction for our users by making it easier to understand test results and find the root cause of test failures and also make triaging bug reports easier for maintainers in the future because they will be able to request a test report which contains all relevant information.

Deliverables/tasks

• Add a converter from XML to HTML for Open Test Reporting format:
  • Add HTML report generator ota4j-team/open-test-reporting#159
  • Use GSON instead of Jackson to avoid affecting downstream projects ota4j-team/open-test-reporting#167
  • Use BND to include OSGi metadata in JAR manifests ota4j-team/open-test-reporting#170
  • Add JUnit-specific metadata to open-test-reporting's HTML report #4116
  • Document HTML report generation ota4j-team/open-test-reporting#174
  • Set up Playwright properly for GitHub Action workflows ota4j-team/open-test-reporting#178
• Add optional support for source control metadata (for example, Git commit ID) to test reports
  • Introduce Git namespace extensions ota4j-team/open-test-reporting#180
  • Include Git metadata in Open Test Report XML output #4126
• Add support for attaching files such as screenshots to test results
  • Add file attachment support to open-test-reporting XML schema
  • Provide APIs to attach files to test results in JUnit
• Drive adoption of Open Test Reporting format by reaching out to test framework maintainers in other ecosystems and ask for feedback