openqa-bats-review: Process JUnit XML instead of TAP

[ricardobranco777]

BATS tests are now producing both JUnit XML (for openQA processing) and TAP logs for human consumption. We have other upstream tests that use only JUnit XML that would benefit from this post fail hook: docker_testsuite & podman_e2e.

Related ticket: https://progress.opensuse.org/issues/186786

TODO

• Update unit tests.
• Update openqa-label-known-issues-and-investigate-hook to check testsuite names instead of BATS_PACKAGE.

Verification runs:

$ openqa-bats-review -n https://openqa.opensuse.org/tests/5338518#
INFO: Processing clone chain: 5338518 -> 5337019 -> 5337015 -> 5337007 -> 5337004 -> 5336991 -> 5336982 -> 5336974 -> 5336966 -> 5336959 -> 5336953 -> 5336947 -> 5336943 -> 5336928 -> 5336922 -> 5336915 -> 5336904 -> 5336900 -> 5336892 -> 5336890 -> 5336884 -> 5336840 -> 5336836 -> 5336077
INFO: Job 5337019 has no logs, skipping
...
INFO: Only one jobs with logs in chain. Exiting

openqa-bats-review -n https://openqa.suse.de/tests/19239056
INFO: Processing clone chain: 19239056 -> 19238546
INFO: No common failures across clone chain. Tagging as PASSED.

[d3flex]

Can you remind me why openqa-bats-review has to be in this repo and not in osado?

[ricardobranco777]

Can you remind me why openqa-bats-review has to be in this repo and not in osado?

To be run as a post hook script, but now we have this issue: https://suse.slack.com/archives/C02CANHLANP/p1758633673618689