In junit-team/junit5#1558 there was the following comment:

rerunner-jupiter's and JUnit Pioneer's annotations didn't really do it for us either - they both introduced a new annotation for flaky tests which replaces the @Test annotation. This is less than great for two separate reasons:
(1) When we want to disable a test, we don't go and replace the @Test annotation with a @DisabledTest annotation - we add the @Disabled annotation next to the @Test annotation. Having flakiness annotations behave differently is inconsistent.
(2) When you want to mark a @ParameterizedTest as flaky, now you need yet another annotation. (And this will compound the more things you want to annotate about the test, or the more ways you have of running a test.)

Technically, we can accommodate this request. Currently @RetryingTest stores run results in a test-level ExtensionContext::Store. If we elevate this to the class-level, it's possible to store the result of a @Test and re-run it using a test template. Alternatively, we check with an ExecutionCondition if the test template ran first and abort the @Test if it were already successful.

Is it ugly? Yes. For example, if the user specifies that the test should re-try 3 times, then the test template has to run at most 2 times because it runs once as a @Test. Ouch. Also, you have to do a bit of magic to ensure whether you are currently evaluating a test template or a @Test result.

Alternatively, we could introduce a @SelfDestruct annotation that deletes a test if it fails. Java::Geci to the rescue?