[7.14](backport #26617) [CI] fight the flakiness with some retry option in the CI only for the Pull Requests

[mergify]

This is an automatic backport of pull request #26617 done by Mergify.

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

[v1v]

For instance,

This particular PR for the build 1 failed:

And when all the pending stages finished, then the pr-merge still continues

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: v1v commented: /test

• Start Time: 2021-07-01T15:40:00.388+0000

• Duration: 52 min 5 sec

• Commit: 688b40d

Trends 🧪

Test errors

Expand to view the tests failures

Extended / metricbeat-windows-2012-windows-2012-r2 / TestPdhSuccessfulCounterRetrieval – github.com/elastic/beats/v7/metricbeat/helper/windows/pdh

Expand to view the error details

 Failed 

Expand to view the stacktrace

 === RUN   TestPdhSuccessfulCounterRetrieval
    pdh_windows_test.go:125: 
        	Error Trace:	pdh_windows_test.go:125
        	Error:      	Expected nil, but got: 0x800007d6
        	Test:       	TestPdhSuccessfulCounterRetrieval
    pdh_windows_test.go:126: 
        	Error Trace:	pdh_windows_test.go:126
        	Error:      	Should not be zero, but was 0
        	Test:       	TestPdhSuccessfulCounterRetrieval
--- FAIL: TestPdhSuccessfulCounterRetrieval (0.00s)
 

❕ Flaky test report

No test was executed to be analysed.

[v1v]

/test

[v1v]

Unfortunately, there are a couple of issues:

1. Test population with the retry does not reset the test failures
2. Dynamic stage does not reset the overall build status