Run (basic) e2e tests for AWS provider on CI

[wainersm]

Currently we run e2e tests on CI for Libvirt and working to get it for docker too. Likewise, ideally we should have CI up and running for the other cloud providers. This issue tracks the work required to have a bare-minimum CI for AWS.

The suggested scope is:

• trigger daily jobs (not pull request) only so that we can understand the costs per run as well as we can better control the bill
• e2e tests provisioner can instantiate an EKS cluster or relies on existing on-prem kubernetes. The former will incur on cost as well, so I think we could start with the on-prem (i.e. install k8s on the test runner). I also don't know if the provisioner for EKS is still working.
• disable confidential VM as, again, CVM incur on costs as well as only a few regions provide instances. So do not install KBS. We will be really running tests for the basic non-confidential features

Cc @ldoktor