Put together temporary staging pipeline solution

This template is ONLY used for feature requests. Bug reporting or pipeline enhancement issues should use the other template options for issue submission.

Description

While testing the gitlab upgrade, we needed to put together an impromptu staging pipeline to confirm that the runners were working as expected. This work was primarily manual, the operator may not be implemented for awhile, and we will need the staging pipeline to work for other tasks. To resolve this need, we want to make a simple, temporary solution for setting up a test pipeline in staging.

Purpose

The temporary staging pipeline solution will allow us to quickly spin up a staging pipeline for things like, #307 (closed), #311, and platform-one/private/big-bang/ironbank/ironbank-bootstrap#430.

Plan

Manual Config:

• Add necessary CI vars (added the artifacts need to get the jobs b
• Add artifacts to skip certain stages
• Get the following stages working:
  • Preprocess
  • Preflight
  • Import Artifacts
  • Build
  • Vat

Automation:

• Create group in ironbank tools
• Add pipeline to group
• Add common test images Pulling prod images instead
• Write script for exporting/importing ci-variables to/from staging and prod group.
• Write script for automating adding all images to staging gitlab and adding appropriate ci-variables

Possible Blockers/Challenges

We can't put a ton of work into this since we're planning to resolve this with the operator, but we'll want to have a good solution since the staging pipeline gets destroyed anytime we have to delete the gitlab namespace.

Acceptance Criteria

• Staging pipeline can be setup with a simple script
• Pipeline can run preprocess, preflight, import-artifacts and build