Problem Description: Today we can stagger code changes to our community galaxy-ng instances (dev, stage, and prod). But we cannot do so with our environment and config changes, examples: proxy changes to fix upload bugs, github auth changes.

Proposed Solution: Restructure our files, deployment triggers, etc. in galaxy-deploy repo to allow for updates that don't involve manual edits to live OCP environments.

Note: we do currently have a work-around for this: manually editing configs within OpenShift to test them in the dev environment before committing the changes that deploy to all environments