(Chore): Parse system out from test suites

[TylerJang27]

Bazel frequently outputs a JUnit like:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites>
    <testsuite name="batch_bin_tests" tests="1" failures="0" errors="1">
        <testcase name="batch_bin_tests" status="run" duration="0" time="0">
            <error message="exited with error code 101"></error>
        </testcase>
        <system-out>running 2 tests...</system-out>
    </testsuite>
</testsuites>

Leading us to just output a pretty sparse and unhelpful error message. I updated our parsing so that if there's only one test case and it's nonsuccess, we will include the suite-level system out. Verified manually as well with an internal.bin

[trunk-io]

😎 Merged successfully - details.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.74%. Comparing base (282d74d) to head (c8d54dd).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1126      +/-   ##
==========================================
+ Coverage   82.37%   82.74%   +0.36%     
==========================================
  Files          69       69              
  Lines       15381    15482     +101     
==========================================
+ Hits        12670    12810     +140     
+ Misses       2711     2672      -39     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[trunk-staging-io]

     

Failed Test	Failure Summary	Logs
variant_quarantine_test should be quarantined when run with variant	A test expected the sum of 2 + 2 to be 5, but it was 4, indicating a failing assertion.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs