Add an OpenShift Deployment for an EMDT Traceability Traction Tenant Controller for use with the VC Traceability Test Suite

Tagging folks: @WadeBarnes @esune @PatStLouis @krobinsonca

Patrick has developed a Traceability Traction Tenant Controller (TTTC - github reference to be added) that interacts with the Traceability Test Suite (TTS - link to be added). The intention of the TTS is that each participant standup an active Web component that can be used to test conformance with any other participant of the TTS. The purpose of this issue is to request cooperation in standing up an OpenShift workspace to hosts the TTTC such that it can be used by other TTS participants.

My thoughts on what needs to be done. I expect that others — especially Wade, Emiliano and Patrick will extend/update/correct this list to make it accurate and to enable the work be done over the next short while. As I understand it, there is not a lot to do this, and so the hope is that this can be done with a meeting or two, Discord discussions as needed, and everyone doing a little bit off the side of their desks. If this is a bigger thing — we’ll determine that quickly.

### Tasks:

- [x] Patrick creates a Helm chart for the TTTC
- [ ] Patrick will transfer his github repo for the TTTC to the BCGov github organization.
- [ ] Wade will create an “EMDT-TTTC-DevOps” github repo to be used for managing the application in GitHub.
- [x] Wade will requestion an OpenShift Workspace for this.
- [x] For now, only the “dev” instance of the OpenShift workspace will be used.
- Given this is a “no guarantees” service we are deploying is there any reason to also have a test or test+production environments? If this does turn into something, we can add such things later, but it is not likely to happen.
- [ ] Patrick (or @krobinsonca ?) will request a Traction **Dev** instance Tenant, and giving Patrick access.
- Given this is just for intermittent testing, is Dev Traction the right place?
- [ ] Wade will point Patrick to what is needed in the “EMDT-TTTC-DevOps” github repo (Helm Chart, secrets, config files, etc.)
- [x] Wade will point Patrick to minimum viable deployment requirements — e.g. adding a monitor on the service, etc.
- The intention is that Patrick will do most of the work.
- [x] Patrick will oversee the deployment.
- Collaborate on any issues that come up.
- [ ] Patrick will arrange for the deployed app to be added as a participant in the TTS.

Thoughts on other things to be done?

An interesting question is if Patrick needs access to the OpenShift instance. Ideally not, but will that just create an undue burden on others?