Discovery and cataloging of existing edxapp pipeline

[robrap]

• Document the various edxapp pipelines, stages and jobs in GoCD.
• Determine which would need to remain as-is, or partially, in GoCD.
  • For example, if build_edxapp_amis:prerelease_materials handles the sync with edx-platform-private, that will need to live on.
• Is investigation into the configuration repo or tubular code needed for this discovery?
• We need a rollout plan for transitioning the pipeline.
  • Will we be slowly transforming the existing pipeline to introduce ArgoCD, or will we be introducing a brand new pipeline?
  • How do we deal with migrating processes that should only happen once (e.g. migrations, edx-platform-private sync, etc.)?
  • If we have a containerized stage environment, would we want e2e tests to ever run against this temporary environment?
  • Other questions regarding transitioning the pipeline?
• Can we document requirements to maintain parity with our current pipeline?
  • For example, we want to maintain the ability to auto-deploy to Production.