chore: add resiliency when provisioning the stack

[mdelapenya]

What does this PR do?

It adds a retry-wih-sleep when executing the installation of the Ansible roles to provision the stack (docker, kubectl...)

Why is it important?

We have seen certain instability accessing the network recently, and we hope to mitigate those issues with the retry strategy.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have run the Unit tests (make unit-test), and they are passing locally
• I have run the End-2-End tests for the suite I'm working on, and they are passing locally
• I have noticed new Go dependencies (run make notice in the proper directory)

Author's Checklist

• @adam-stokes do you foresee any other Ansible call downloading stuff?

[elasticmachine]

❕ Build Aborted

Either there was a build timeout or someone aborted the build.

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

Expand to view the summary

Build stats

• Start Time: 2022-01-11T10:54:00.301+0000

• Duration: 62 min 22 sec

• Commit: 776c62a

Test stats 🧪

Test	Results
Failed	5
Passed	211
Skipped	0
Total	216

Test errors

Expand to view the tests failures

Initializing / End-To-End Tests / kubernetes_autodiscover_elastic-agent / Logs collection from running pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-pod": failed to copy events from test-bdd4091e-c1ae-4779-adfd-1726b864182e/elastic-agent-th6s6:/tmp/beats-events: stat /tmp/test-1842835733/events: no such file or directory 

• no stacktrace

Initializing / End-To-End Tests / kubernetes_autodiscover_elastic-agent / Logs collection from a pod with an init container – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:container-in-pod" 

• no stacktrace

Initializing / End-To-End Tests / kubernetes_autodiscover_elastic-agent / Logs collection from short-living cronjobs – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.container.name:cronjob-container": failed to copy events from test-b0b44440-7460-4487-92e8-56ddecefa54e/elastic-agent-kkvqp:/tmp/beats-events: stat /tmp/test-730636594/events: no such file or directory 

• no stacktrace

Initializing / End-To-End Tests / kubernetes_autodiscover_elastic-agent / Logs collection from failing pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:a-failing-pod": failed to copy events from test-6e94a588-0a50-40c3-982c-0279aaf41986/elastic-agent-grg76:/tmp/beats-events: stat /tmp/test-3931697739/events: no such file or directory 

• no stacktrace

Initializing / End-To-End Tests / kubernetes_autodiscover_elastic-agent / Metrics collection configured from targeted Redis Pod – elastic-agent standalone

Expand to view the error details

 Step "elastic-agent" collects events with "kubernetes.pod.name:redis": failed to copy events from test-421a22ab-4039-44b6-b743-678b7e538e4f/elastic-agent-zbf4z:/tmp/beats-events: stat /tmp/test-919876881/events: no such file or directory 

• no stacktrace

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[mdelapenya]

/test

[mdelapenya]

The 5 failing errors, not related to this PR; are reported in here #1992

[tetianakravchenko]

Thank you for the fix!