Create GitHub Actions workflow for running tests

[samdoran]

Run sanity, unit, and integration tests in GitHub actions. We should be able to disable some Zuul jobs after merging this.

Also upload code coverage reports.

We may want to look at a matrix of Python version X Ansible version. Currently it only tests one Ansible version per Python version.

[AlanCoding]

It looks like this is running the docker and podman tests? This is fantastic. The whole thing ran in under 5 minutes too.

[samdoran]

Yup, just running the tests in a VM hosted by GitHub Actions. Ideally we would run those tests in our test container, but I haven't worked how to run podman inside of a Docker container where we don't control the command used to invoke the container.

[samdoran]

Adding the image build steps brings overall execution up to a little over nine minutes. Not too bad, but building that image every time is costly.

[Shrews]

Note for @shanemcd and myself to review this after the holidays to make sure we would be covered on both GHA side and Zuul side (global job references?).

[Shrews]

Note for @shanemcd and myself to review this after the holidays to make sure we would be covered on both GHA side and Zuul side (global job references?).

FYI, there are references to some of the runner jobs in the ansible/ansible project at https://github.com/ansible/project-config/blob/2bd212f0b14ae32bf687865f95cb7c695808ed4f/zuul.d/projects.yaml#L853-L877.

[Shrews]

I tried to validate that we were actually using the image created from the new GHA job that creates the image for the integration tests. I expected PR #960 to fail the integration tests, but they did not (and it does seem the exception is being written to the proper location for the callback in the container image). It might be explained by the comment left by @AlanCoding.

I know @samdoran put a lot of work into this (thanks Sam!), but given that this doesn't seem to be testing the image created from the PR in the integration tests, I'm not on board with merging this.

[Shrews]

I tried to validate that we were actually using the image created from the new GHA job that creates the image for the integration tests. I expected PR #960 to fail the integration tests, but they did not (and it does seem the exception is being written to the proper location for the callback in the container image). It might be explained by the comment left by @AlanCoding.

I know @samdoran put a lot of work into this (thanks Sam!), but given that this doesn't seem to be testing the image created from the PR in the integration tests, I'm not on board with merging this.

I believe that I've now found a way to make this work properly for integration tests. I'll be updating this PR.

[Shrews]

Commit 08e3284 on PR #960 shows that the change I just pushed here should work properly for integration testing.