New GitHub Action workflow to build + deploy site

[trevormunoz]

This revised workflow should replace the current cron job + Airtable release workflow with one that builds in GitHub Actions on any push or pull request to the master branch then deploys to the server via rsync.

A couple additional notes:

• Currently this runs persist and commits a fresh copy of data on every build (may or may not be desirable)
• Uses a dedicated public/private keypair
• If merged, we can also remove the release roles from mith-ansible

This should also be fairly straightforward to update when the v0.4.0 branch is merged.

[netlify[bot]]

✅ Deploy Preview for mith-static ready!

Name	Link
🔨 Latest commit	7c161de4138e0f9f332f2621f1e83ddaadd373ba
🔍 Latest deploy log	https://app.netlify.com/sites/mith-static/deploys/62a21959c2e1790009437cdf
😎 Deploy Preview	https://deploy-preview-17--mith-static.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[trevormunoz]

The new Action fails in this repository because of the security policy around secrets, I believe:

Note: With the exception of GITHUB_TOKEN, secrets are not passed to the runner when a workflow is triggered from a forked repository.

The same step does not fail in the fork: https://github.com/trevormunoz/mith-static/runs/6816382322?check_suite_focus=true

[trevormunoz]

I believe this has now been superseded by @raffazizzi 's recent changes