ci: drop travis ci and appveyor in favor of GitHub actions #2234
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
Description of change
travis ci updated their pricing model to cap open source projects.
https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing
https://www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
GitHub actions is another free for open source continuous integration platform, which has more generous terms.
https://docs.github.com/en/free-pro-team@latest/actions/reference/usage-limits-billing-and-administration
AppVeyor was being used exclusively for Windows CI testing, GitHub actions can test on Linux, MacOS, and Windows.
To simplify the CI process, dropping AppVeyor as well, and moving forward with GitHub actions as the sole CI provider.
GitHub actions was originally configured in #2217 and #2218
the documentation has been updated to reflect these change, replacing existing CI badges for uP 5 with the new GitHub actions badge