improve: allow flaky tests run with specify parameters

[hezhangjian]

Fix #3249

Motivation

This PR addresses the issue where tests annotated with @FlakyTest were not being executed by JUnit unless they were also annotated with @test.

To resolve this, we have updated our Maven Surefire plugin configuration to exclude tests tagged with flaky during regular CI runs, allowing these tests to be run separately.

This adjustment ensures that all tests, including those marked as flaky, are executed as intended unless explicitly excluded.(In CI still don't run it)

Moreover, I've planned the addition of a daily CI job and non-required CI to specifically run tests tagged as flaky, ensuring continuous monitoring and quicker identification of intermittent issues without affecting the main test pipeline. This setup also enhances the ability to run tests directly from the IDE, making it more convenient for developers to execute and debug individual tests as needed.

[hezhangjian]

@lhotari PTAL, after half year, I finally closed this thing. :)

[eolivelli]

+1 thanks

[lhotari]

This change isn't consistent with the PR description "This adjustment ensures that all tests, including those marked as flaky, are executed as intended unless explicitly excluded".
Wouldn't this exclude the flaky group by default?

[hezhangjian]

@lhotari I would like to excluded flaky tests in maven command line, but can be easily run in IDE.

[lhotari]

Is this the original meaning of the "flaky" test group in the project? If so, please document this in the FlakyTest annotation. The PR description should also clearly express this that in CI, the tests aren't run at all.

[lhotari]

Please check the review comments

[hezhangjian]

@lhotari I updated the annotation's annotation, PTAL again, thanks

 * <p>Flaky tests are tests that produce inconsistent results,
 * occasionally failing or passing without changes to the code under test.
 * This could be due to external factors such as timing issues, resource contention,
 * dependency on non-deterministic data, or integration with external systems.
 *
 * <p>Tests marked with this annotation are excluded from execution
 * in CI pipelines and Maven commands by default, to ensure a reliable and
 * deterministic build process. However, they can still be executed manually
 * or in specific environments for debugging and resolution purposes.