Reduce test retry count to zero

[Renkai]

Our current tests will auto-retry failed tests, which could lead to some problems:

• If one method in one test class failed, all methods in the test class will be retriggered, which will make the test easier to timeout and generate more noise logs to make us harder to locate the error log.
• The failed method may have changed the test environment, and then the second try may report different error info, which will mislead us to solve the problem, too.
• Auto retry is useful to pass flaky tests, but have a low return on investment for the same reason shown above.

[Renkai]

/pulsarbot run-failure-checks

[Renkai]

/pulsarbot run-failure-checks

[eolivelli]

Thanks @Renkai

I had already files the same patch at #9043

There is an open discussion.
Can you please add your opinion in that patch?

I am totally +1 on this patch

[Renkai]

@eolivelli Seems set retry count to 0 really have a significant effect on the success rate on our code base, maybe it's not suitable to be merged now, I will leave this patch to see which tests are easy to be flaky

[sijie]

Before merging this, we should have a clear idea about how this PR will impact CI.