chore: decouple ansible install from execution

[mdelapenya]

What does this PR do?

It separates the single, current shell script execution for provisioning the stack VM in three parts:

1. check if virtualenv is created if the .venv-installed file is not present, create virtualenv and create the file
2. install Python and Ansible dependencies if the python-dependencies file is not present, install them and create the file
3. execute the command passed to pyrun

We have added a retry logic for the first two scripts, so that we can control and locate possible network issues for each part of the provisioning code

Why is it important?

Decouple provisioning from execution

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)

Follow-ups

As @adam-stokes mentioned, having a cache/mirror for the Ansible dependencies could improve the resiliency

[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

• Start Time: 2022-02-22T14:28:22.810+0000

• Duration: 52 min 13 sec

Test stats 🧪

Test	Results
Failed	0
Passed	253
Skipped	0
Total	253

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

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

• /test : Re-trigger the build.