Test and Calculate Code Coverage on PRs

[hop-along-polly]

A testing tool should be pretty freaking well tested am I right? With that in mind the test-suite should pass before a PR can be merged into the main branch. We also want to maintain as high of test coverage as possible since the point of AlwaysON is to help developers achieve 100% code coverage w/o the difficulty of setting up test infrastructure.

Acceptance Criteria

• [ ] The test-suite is run when a new PR is opened or an existing PR is updated
• [ ] The test-suite is NOT run when commits are pushed to a branch associated with a Draft PR or a branch that is NOT associated with any PR.
• [ ] The PR is blocked until the test-suite has run successfully.
• [ ] Code Coverage is reported somewhere on the PR.

Stretch Goal

• [ ] The Code Coverage appears as a badge at the top of the README.md file. Sort of like this https://daily.dev/blog/readme-badges-github-best-practices or this https://github.com/marketplace/actions/code-coverage-summary.

[hop-along-polly]

@chrishalbert Reporting the code coverage with a badge isn't required but if there's an easy way to automate this it would be great seeing that appear on the README.md