Github Action + functional tests (no *hog tests)

[tsebastiani]

Closes #374

This PR introduces the new functional tests GitHub Action on a disposable OpenShift instance 4.x leveraging the crc-cloud project created on purpose.
The GitHub action is triggered by commenting a pull request with the keyword /test (the keyword can be changed) and to make it work must be first merged in the main branch.
The action will instantiate and dispose a fully functional OpenShift instance on AWS. The action will checkout the last commit in the PR branch from which the comment is added and the OpenShift instance will be disposed even if an error is encountered during the test run.
The following tests are actually executed;

Name
test_app_outages_gh
test_container
test_namespace
test_net_chaos
test_time

The following secrets must be created in the repository :

Secret	Description
AWS_ACCESS_KEY_ID	AWS access key ID
AWS_SECRET_ACCESS_KEY	AWS secret access key
KUBEADMIN_PWD	password for the kubeadmin account in the newly created OpenShift Instance
DEVELOPER_PWD	password for the developer account in the newly created OpenShift Instance
REDHAT_PWD	password for the redhat account in the newly created OpenShift Instance
PULL_SECRET	a base64 encoded pull secret that can be downloaded from here after registrating or logging in with a RedHat account

The Action will produce a test report containing the Passed/Failed tests and the code coverage in the action summary. From my experiments the full run takes approximately 23 minutes.

[paigerube14]

Have you added the secrets to this main github page already? We might want to merge the workflow and then the code changes separately to be able to run the workflow against the test changes. Thoughts?

[tsebastiani]

Have you added the secrets to this main github page already? We might want to merge the workflow and then the code changes separately to be able to run the workflow against the test changes. Thoughts?

Paige regarding the AWS credentials and the pull secret we should ask to the management to provide us them, regarding the passwords instead we can simply generate them randomly and they will work, anyway I'm afraid that I don't have the grants to set them in the krkn repo :-\ @chaitanyaenr can you check?

[chaitanyaenr]

@tsebastiani sent you an invite, do let me know if it allows you to add secrets to the project. Thanks.

[tsebastiani]

@tsebastiani sent you an invite, do let me know if it allows you to add secrets to the project. Thanks.

I can access some settings, but not the actions and secret section apparently.

[paigerube14]

/lgtm

[chaitanyaenr]

LGTM

[chaitanyaenr]

we can merge it in once rebased. Thanks.