MAINT: Split actions workflow between CI and Release

[kaitj]

Proposed changes

This splits the actions workflow into separate testing and release workflows. Additionally reverts releases to manual trigger, which was done to avoid those skip_changelog automatic version bumps.

PR also introduces separate heroku apps for testing and release. Production heroku app (the current afids-validator) will only be deployed on release. Otherwise, non-release merges that trigger the testing workflow will be deployed to a test heroku app (afids-validator-test).

There are probably some configs we need to set up for the afids-validator-test app

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)
• Other (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!

• Changes have been tested to ensure that fix is effective or that a feature works.
• Changes pass the unit tests
• Code has been run through black with the -l 79 flag.
• I have included necessary documentation or comments (as necessary)
• Any dependent changes have been merged and published

Notes

All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.

PR template was adopted from appium

[tkkuehn]

This looks good to me! Is the afids-validator-test heroku app already registered? If so, we can try merging this and getting the config right at the meeting on Wednesday.

[kaitj]

This looks good to me! Is the afids-validator-test heroku app already registered? If so, we can try merging this and getting the config right at the meeting on Wednesday.

I believe so. I had it already created, but hadn't set up any of the configs or anything like that yet (I don't think). Been a while though so would need to double check.