Define/create a series of incremental development environments, including any build system cleanup to enable this.

A unified build pipeline that is used by operators to deploy a production CORD POD as well as by developers and testers to work with specific CORD components. This pipeline satisfies the needs of at least four different groups:

Operators can quickly and reliably deploy an official release of CORD onto production hardware.

Component and Platform developers (e.g., XOS services, GUIs) can develop a specific component in isolation, with a tight development loop, using the dev tools they choose (e.g., IDE).

*Integration developers *can develop and verify code changes in the E2E system, with a reasonably tight development loop, using a reasonable set of dev tools.

*Testers *can test components in isolation as well as the E2E system. It is important for testers to be able to reliably and reproducibly build all components from source.

https://docs.google.com/document/d/1zss7ChiCh9zjX1lAn-l6r5WTPAFTvNXxA5DOY-EgCQ4/edit?usp=sharing

This work will also include build system cleanup:
Building and tagging containers, replacing gradle with make
Unused code needs to be deleted
Playbooks and roles that aren't used
Dockerfiles for no longer used components

Redundant code should be reconciled
Container builds happening in many places