Repository navigation
Problem this solves:
No harbor support for prod envs
Why this is a problem?
We want to make a move over to harbor for all envs, but we cannot because this action is used for releasing prod deployments.
Solution:
Add a harbor login as well as the tagging for the harbor release. Allow for either an AWS repo or Harbor repo, giving dual support for now, then cutting over to only harbor for v2.