ci: exclude failsafe summaries from JUnit reports

[dkropachev]

Moves the CI-only report filtering change out of #999.

Restricts test report publication to TEST-*.xml, excluding Maven Failsafe summary XML files that are not JUnit testcase reports.

[coderabbitai]

Warning

Review limit reached

@dkropachev, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Limit details: You’ve used all 3 included reviews currently available.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: QUIET

Plan: Pro Plus

Run ID: 544fc453-108f-4c88-a2b0-57c35136984d

📥 Commits

Reviewing files that changed from the base of the PR and between ee0d033 and 732bce3.

📒 Files selected for processing (1)

• .github/workflows/tests@v1.yml

---

_{Comment @coderabbitai help to get the list of available commands.}