Using a Vagrant libvirt based virtual machine
and OpenShift Local.

This commit breaks vagrant test!
To be able to run OpenShift Local inside a local provisione tmt virtual machine you need to change tmt sources:
change DEFAULT_CPU_COUNT in tmt/steps/provision/testcloud.py to 6
2 cpus are not enough for Openshift Local and is is not custumizable (will open an issue in tmt but our goal is to provision the machine in the cloud so this is not strictly necessary, for local usage is probably better to make vagrant work again)

…ebase

Before using the deploy role in the deploy playbook.
Wait for the deploy tests to be reviewed, up and running.
Every change in the deploy playbook has to be repeated manually
back in the deploy role, in the meantime.

Co-authored-by: Laura Barcziová <[email protected]>

Co-authored-by: Matej Focko <[email protected]>

Instead of python-cryptography.
CentOS 8 Stream was not able to resolve python-cryptography.
We don't need to support old CentOS versions anymore,
so we can use the python3 package.

Co-authored-by: Laura Barcziová <[email protected]>
Co-authored-by: Matej Focko <[email protected]>

Tokman is no longer used.
The github-app-private-key is now used directly by the service and the workers.

Co-authored-by: Matej Focko <[email protected]>

Now we are using testing farm for it.