Enable test retry in CI

[bric3]

What Does This Do

Retry tests in CI, I wonder however if these should be tracked ? Maybe Test Optim has that?

Note:
When a test fails it is captured by Test Optimization.

@git.branch:test-retry-in-ci @test.status:(fail OR pass) @test.suite:PekkoHttpServerInstrumentationAsyncHttp2Test @ci.job.name:"test_inst: [17, 5/6]"

Motivation

Additional Notes

Contributor Checklist

• Format the title according the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any usefull labels
• Don't use close, fix or any linking keywords when referencing an issue.
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, move, or deletion
• Update the public documentation in case of new configuration flag or behavior

Jira ticket: [PROJ-IDENT]

[smola]

+1 to this. Big advantage of the test-retry plugin as opposed to JUnit/Spock-level retry mechanisms is that intermediate test runs are not lost. So we can keep observability of intermediate failures in Test Optimization (I checked this in Circle CI back in the day, I haven't verified with Test Optimization though).

I think eventually we'd need a more nuanced approach here the way I outlined at #8113, and also stop skipping @Flaky tests and rely on this mechanism. But there's more work involved there. I think it is a good idea to start with this PR if it works well.

[PerfectSlayer]

So we can keep observability of intermediate failures in Test Optimization

It was my main concern about the feature. I'm glad @bric3 came with a new pair of eyes and gave it another try with the new CI 👍