Research streamlining or eliminating setup-test-env

Research prompt

Can the gitaly, shell, and workhorse setup and configure jobs in setup-test-env retrieve built components from a generic package registry or another storage platform (like GitLab releases, GCS) that get built in the project?

This can help reduce the frequency of software builds across CI and local GitLab Development with the GDK.

Potential benefits

• Reproducible process of building and publishing binaries/packages that can leverage CI
• Align builds for local, CI, Cloud development
• Make pre-built gitaly, shell and workhorse available for all development environments through retrieval instead of building