1. Create a test runner-agnostic internal API for retrying tests.
2. Identify some tests that need retrying (see JAVA-5392).
3. modify how the identified tests are run such that they are retried.
4. Keep routinely identifying such tests and modifying them. This item should not prevent us from making the ticket as closed.

Note that @RepeatedTest from JUnit 5 does not seem to work with @ParameterizedTest: https://github.com/junit-team/junit5/issues/1224, nor does it have functionality we need (we need to be able to inspect the test failure as well as the test parameters).

Given that @RetryingTest from https://junit-pioneer.org/docs/retrying-test/ has access to the test failure (see onExceptions), we should be able to access the test failure and, hopefully, the test parameters from JUnit 5 when developing our retry mechanism.