Adding automated CI testing via Github Actions

[joewesch]

This PR leverages Github Actions to run the current module tests in 4x versions of python (3.7+) running on 2x versions of both Ubuntu and MacOS. I initially wanted to include python2, but ultimately decided the juice wasn't worth the squeeze.

In order for the tests to pass I had to update Jinja2 to 3.0.1 for python 3.10 compatibility as well as change the SSH test to run on a different port since the VMs the tests were on utilize port 22.

I also needed to tweak the Git module test to look for a hostname in the key rather than exactly equal. Long story short, git-upload-pack now adds \0version=#\0 to the end of the transport so the hostname was coming up as 'HOST': 'localhost\x00\x00version=2' in the logs. This seemed like it was just because you are using the gitpython module and not running a git CLI command to run the test so I didn't think it needed to be taken into account in the module itself. Plus, it may prove fragile in the future if they add additional extra parameters between the host=X and version=X, but that's a potential problem for another day.

See here for an example of the CI in action: https://github.com/joewesch/opencanary/actions/runs/1856565837

[HybridAU]

This is amazing. I was looking at the issue with SMB logs, and thinking "this is a simple regression, we should really have a unit test for that". Then I was thinking we really need unit tests to run automatically.

[jayjb]

This is so great! Thank you so much. Ill try get the other platforms and python2 working too.