Reintroduce this feature we already have for JUnit4-based tests.
It looks like some random flakiness is unavoidable (possibly linked to network issues or anyway causes independent of the framework or of a particular test implementation).
Some other possible solution inspiration sources (although the surefire-based approach seems more preferrable):
- @RetryingTest from JUnit Pioneer
Timebox: 5sp for investigation/PoC.