github workflow pain points

[balmas]

Some observations on remaining pain points with the current GitHub workflow:

1. the qa and release builds are done manually on the local machine and not a clean environment
2. the merge of master to qa is a little messy sometimes (maybe caused in part by previous point). Sometimes the node_modules or package-lock files are getting out of whack and it requires deleting the qa branch and starting over to get a clean build.
3. when running tagged-commit, you have to push the branch and the tag separately, causing 2 duplicative travis invocations
4. I would like a better solution for the environment files from the protected-config repo that are required for a functioning build. Current build process requires a local copy of the protected-config repo. We should probably move as much as we can from that file to our new config service and anything that remains should be handled via an encrypted secret.
5. I'm not sure I like the production tags that are only the build number and no release information. (e.g. 20200618494)

[balmas]

1, 3 and 4 have been addressed by the switch to GitHub actions.