airbyte-ci: embed junit xml reports into user-facing html report

[postamar]

Fixes #34039

Tested this locally and with https://github.com/airbytehq/airbyte/actions/runs/7820041779
Expand "java unit tests" or "java integration tests" to see the new goodness:

We can worry about how to make it look at a later date. The original Junit XML format is tolerably readable as long as the system-out and system-err data are indented properly.

Note that gradle does render very pretty html reports but these are not single-page and copying them to a "subfolder" in our GCS bucket will mess with the relative refs in the html. I've given up that route completely in favour of embedding the test reports inside the overall html report. This also has the nice advantage of producing the same results locally vs. remotely.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Feb 7, 2024 7:18pm

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ TransportError: Unexpected response from engine: Server error '502 Bad Gateway' for url 'http://127.0.0.1:38451/q... dagger.client._core in execute View Issue
• ‼️ TransportError: Unexpected response from engine: Server error '502 Bad Gateway' for url 'http://127.0.0.1:41071/q... dagger.client._core in execute View Issue
• ‼️ TransportError: Unexpected response from engine: Server error '502 Bad Gateway' for url 'http://127.0.0.1:32981/q... dagger.client._core in execute View Issue
• ‼️ QueryError: lstat build/test-logs/2024-02-15T01:20:15-test: no such file or directory pipelines.airbyte_ci.steps.gradle in _collect_logs View Issue
• ‼️ TransportError: Unexpected response from engine: Server error '502 Bad Gateway' for url 'http://127.0.0.1:43001/q... pipelines.airbyte_ci.steps.gradle in _collect_logs View Issue

_{Did you find this useful? React with a 👍 or 👎}