convert beta galaxy migrations to run via a job

Problem Description: beta galaxy runs migrations via init containers in the API pod. However at the scale that beta-galaxy-prod is expected to run, this could cause conflicts or race conditions with multiple migrations attempting to run simultaneously during a deployment.

Proposed Solution: Mimic legacy galaxy's migration job utilizing ArgoCD hooks to rollout a new migration job prior to rolling out the remainder of the services.