fix: BazelJUnitOutputListener logging xml output on suite-level failures

[amishra-u]

fixes: #327

1. Updated code to propagate the test suite failure to each test case.
2. The test suite failure will be propagated to each child node, even if the test is not executed.
3. Additionally, this change fixes the bug introduced in Add support for @AfterAll in XML report #300, which incorrectly logged the test_suite as a testcase and logged incorrect values for the "tests" attribute in the node.

[fzakaria]

my hot take:

I wrote some tests that work on actual test classes rather than TestData -- maybe it would be good to continue in that direction.

The unit tests on TestData only take us so far; we need to write more "integration-style" tests running on real classes IMO since the JUnit data structure is kind of opaque.

[shs96c]

@fzakaria, I've no objection to a very limited number of test cases like this, but they tend to be slow to run, require a lot more set up, and can be opaque to debug and understand. If we introduce them, I'd rather they were an absolute minority of tests for this kind of functionality.

[fzakaria]

@shs96c i agree hollistically but the JUnit stuff is so opaque -- feels like starting in the reverse direction is good.
i.e. writing "integration style tests" and then taking that information to encode it as a unit test with the TestData mock.
I guess they can always be tagged and run in a separate step ;P

Anyways -- just my thoughts. As someone who likes to contribute this can help me understand if I'm breaking other consumers.

[amishra-u]

@shs96c Can you please take a look

[shs96c]

LGTM, but could you please run bazel run scripts:format?

[amishra-u]

@shs96c Can you please merge it. I have fixed formatting issue.