We should update jtreg to a newer version of JUnit.

In addition to "Numerous bug fixes and minor improvements" compared to JUnit 5.9.2 the following feature would be a major win for analyzing failing tests:

> Since version 1.10, the JUnit Platform provides built-in support for pruning stack traces produced by failing tests. This feature is enabled by default but can be disabled by setting the junit.platform.stacktrace.pruning.enabled configuration parameter to false.
>
> When enabled, all calls from the org.junit, jdk.internal.reflect, and sun.reflect packages are removed from the stack trace, unless the calls occur after the test itself or any of its ancestors. For that reason, calls to org.junit.jupiter.api.Assertions or org.junit.jupiter.api.Assumptions will never be excluded.
>
> In addition, all elements prior to and including the first call from the JUnit Platform Launcher will be removed.

Find the release notes of JUnit 5.10.2 at https://junit.org/junit5/docs/current/release-notes/index.html#release-notes-5.10.2
Find the release notes of JUnit 5.10.1 at https://junit.org/junit5/docs/current/release-notes/index.html#release-notes-5.10.1
Find the release notes of JUnit 5.10.0 at https://junit.org/junit5/docs/current/release-notes/index.html#release-notes-5.10.0