[PROPOSAL] Add flaky test retry

[dblock]

What kind of business use case are you trying to solve? What are your requirements?
I want to be able to rely on CI when contributing to all plugin projects.

What is the problem? What is preventing you from meeting the requirements?
In a trivial change in opensearch-project/.github#64 I made 20 pull requests with a trivial .md file change. 10/20 have failed in CI, anecdotally because of flakey tests.

What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
Introduce a small number of retries as standard procedure to tests, similar to opensearch-project/OpenSearch#2547, implemented in opensearch-project/OpenSearch#2638. While this doesn't fix flakey tests, it decreases the noise to a level where the worst offenders can be fixed instead of having a 50% failure rate.

What are remaining open questions?
We know how to do this for OpenSearch plugins with Gradle, but we need another mechanism for OpenSearch Dashboards.

[saratvemulapalli]

@dblock looks like this slipped through the cracks.
Do you want to open up issues on all the repos and label them for next release?

[dblock]

@saratvemulapalli if you want to take this campaign up go for it!

[ohltyler]

Similar comment as #138 (comment)