MEA interface for devices services

[reubenmiller]

The introduction of services in 0.10.0 via the tedge/health endpoint was very powerful to allow user to communicate the runtime state of various components running on either the main device, or child devices.

The interface should be as simple as possible allow services to not have to keep track of the name of the thin-edge.io device in the topic, but rather any existing discover service to communicate the required identity information.

Overview

• Dedicated topics that can be used to publish Measurements/Events/Alarms (MEA) to the corresponding service without having to worry about namespacing specifics.
• MEAs should only be published to the cloud once the service has been successfully registered in the cloud

[reubenmiller]

Publishing telemetry data to services is covered in the new tedge MQTT api. thin-edge/thin-edge.io#2030. Implementation will follow.

[reubenmiller]

Will be included as part of 0.13.0