Telemetry Client Deployment

[wpank]

Similar to #2040 (read that first), but a bit less invovled:

The telemetry client part has been separated out into it's own package named telemetry. The sole purpose of this is to subscribe to the a telemetry backend, and write things to the db related to liveness.

Some considerations for deployement:

• there needs to be a otv-telemetry docker image repo created
• the build and publish ci pipelines already exist but need the docker repo to be created first
• There would only need to be 1 replica at first (in the future if things need to be scaled more, mayber more)
• the only things in the config tha are needed are db and telemetry sections
• there doesn't need to be any exposed ports, save for the telemetry and db connections

[ironoa]

* there doesn't need to be any exposed ports, save for the telemetry and db connections

An exposed port is needed for the healthcheck