Create a `maintenance` runner for running automated builds of projects - investigation spike

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

Current Behavior

Currently the 12 hour builds run on the same runners that CHT uses in their daily work.

Purpose

12 hour builds take up quite a bit of resources and cause increased pipeline run duration which decreases productivity for CHT engineers. Moving the 12 hour builds to separate runners allows maintenance of approved images to happen without affecting the workflow for CHT engineers.

Plan

• Spin up another two gitlab runners that only handle maintenance of previously approved images.
• Associate the trigger script with the new runner so it will kick off pipelines on the new runners.

Acceptance Criteria

• Two new runners spun up (regular, and disconnected build).
• Pipeline maintenance runs run on the new runners