Move from Travis CI to GitHub Actions

[fulldecent]

I would like to promote GitHub Actions as the new, better-maintained alternative to Travis CI.

GitHub Actions appears to be the new best practice.

Work plan:

• [ ] Remove .travis.yml in the project folder
• [ ] Add corresponding GitHub Actions CI to the project folder
  • [ ] Please study https://github.com/Alamofire/Alamofire/blob/master/.github/workflows/ci.yml
  • [ ] Please also include our extra feature (quality checks)
• [ ] Update the recipe so that the correct GitHub Actions CI is now included (see the curl commands)
• [ ] Test that it works:
  • [ ] Complete the recipe, ensure that the generated product folder matches the files already in your pull request
    • [ ] Attach screenshot of empty diff -r
  • [ ] Deploy the generated product folder as a new repository on GitHub and ensure that the GitHub Action was successfully triggered
    • [ ] Attach link to the GitHub Action CI task that was triggered

[fulldecent]

See some progress at:

https://github.com/fulldecent/tmp-swift5-module/blob/main/.travis.yml

[fulldecent]

Fixed at c47eb05b7d16756657b36618dae6cbf15c609e3a