Set up non-heroku deploy workflow

[tkkuehn]

Proposed changes

This PR adds a workflow to build a "release" consisting of a built wheel of the AFIDs validator and the a set of environment variables to configure it (drawn from the repository secrets), then deploy it to the production AFIDs Validator server (also configured via the repository secrets).

I've tested this from a branch on my fork and everything seems to be in order, but its worth noting that a couple of things outside of merging this PR will need to happen for the workflow to work:

• [x] The appropriate config variables will need to be added as secrets. (Done but will need to be verified)
• [x] I'll need to take a look at the production server to make sure it's set up to handle the architecture proposed here.
• [x] SSH keys will need to be generated and added to the repo as secrets and to the production server.
• [x] I'll need to configure the production server to accept SSH requests from any IP.

Types of changes

What types of changes does your code introduce? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionalitiy)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Other (if none of the other choices apply)

_PR template was adopted from appium_

[tkkuehn]

Note to self: Pretty much all the prep work is done, just need to update the service definition on the server before merging and trying this out.