Enhancements to GH Actions Pipeline

[mylesagray]

Testing should be part of the pipeline for all PRs and commits to master - must pass with no errors to be merged/released.

https://stackoverflow.com/a/62882641/571593

Release pipeline should probably be two separate pipelines:

• build - builds the application and container image, tags with latest and git SHA
• release - tags an already-built container image with a static version number e.g: v0.0.1 for human readable releases

End to end pipeline should probably look something like this:

• linting - Probably using autopep8 and pylint
• testing - Using built in unittest/nose/pytest and calculate code coverage
• vulns - Static code analysis & CVE scanning
• build - Builds the app container image
• vulns-image - Scan built image for CVEs
• push - Push built image to repo
• release - Manually triggered, or triggered with a push to a specific branch or tag to build a "released" image and creates a GitHub "Release"

[mylesagray]

/reopen more to come :)