Use venv for deployed python tools.

[saltydk]

Deploy all python scripts/tools in their own venv to avoid conflicts when installing or whenever user does something outside of what ansible manages.

[chazlarson]

Cloudplow config upgrade task is failing now, I imagine because it's not running in the venv:

TASK [cloudplow : Settings | Upgrade 'config.json'] ***************************************************************************************************************************************************************************************
Friday 05 November 2021  20:57:33 +0100 (0:00:00.210)       0:00:19.354 *******
fatal: [localhost]: FAILED! => {"changed": true, "cmd": "/opt/cloudplow/cloudplow.py update_config", "delta": "0:00:00.179397", "end": "2021-11-05 20:57:33.635333", "msg": "non-zero return code", "rc": 1, "start": "2021-11-05 20:57:33.455936", "stderr": "Traceback (most recent call last):\n  File \"/opt/cloudplow/cloudplow.py\", line 10, in <module>\n    import schedule\nModuleNotFoundError: No module named 'schedule'", "stderr_lines": ["Traceback (most recent call last):", "  File \"/opt/cloudplow/cloudplow.py\", line 10, in <module>", "    import schedule", "ModuleNotFoundError: No module named 'schedule'"], "stdout": "", "stdout_lines": []}
...ignoring

PR opened to address this.

[owine]

Closed by #39