OperationCode
Rewrite - Switch to Github Actions Instead of CircleCI
With the progress made in Github Actions over the last few years, I think it makes sense to switch over to using that instead of CircleCI. This will eliminate another third party integration and it's an easy way to keep all of the functionality under one roof. Github Actions will allow us to replicate everything the current Circle CI configuration is doing, including pushing to AWS ECR.
@aaron-suarez - how do you feel about switching to Github Actions? We'll need to discuss permissions to add secrets to the Github environment as I don't believe I have that access.
I like the idea just fine. We use GitHub Actions for the front end if I'm not mistaken, so it's already a known thing around the org.
