Rename SensorData to SensorTelemetry

This message holds two different types of data: metric samples and
state snapshots, which when combined into a single message, represent
the telemetry data of a component. The name change reflects this
purpose more accurately.

Signed-off-by: Tiyash Basu <[email protected]>

Author: tiyash-basu-frequenz

RELEASE_NOTES.md

@@ -40,6 +40,7 @@
 - Renamed `MetricSample.source` to `MetricSample.connection` to make it more specific as to what it refers to.
 - Rename `SensorStateCode.SENSOR_STATE_CODE_ON` to `SensorStateCode.SENSOR_STATE_CODE_OK`, to better indicate that we do not control on/off state of sensors.
 - Rename `ComponentData` to `ElectricalComponentTelemetry` to better specify its purpose of encapsulating general telemetry data from electrical components.
+- Rename `SensorData` to `SensorTelemetry` to better specify its purpose of encapsulating general telemetry data from sensors.
 
 ## Bug Fixes
 

proto/frequenz/api/common/v1/microgrid/sensors/sensors.proto

@@ -167,7 +167,7 @@ message SensorStateSnapshot {
   repeated SensorDiagnostic errors = 4;
 }
 
-// SensorData message aggregates multiple metrics, operational states, and
+// SensorTelemetry message aggregates multiple metrics, operational states, and
 // errors, related to a specific microgrid sensor.
 //
 // !!! example
@@ -201,7 +201,7 @@ message SensorStateSnapshot {
 //      ]
 //   }
 //   ```
-message SensorData {
+message SensorTelemetry {
   // The ID of the microgrid sensors.
   uint64 sensor_id = 1;