Update documentation for origin_time field in proto files

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

# Conflicts:
#	proto/frequenz/api/common/v1/microgrid/electrical_components/electrical_components.proto

Author: tiyash-basu-frequenz

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

@@ -173,7 +173,7 @@ message CommunicationComponentDiagnostic {
 //     in time, so there is only a single `snapshot_time`. any parallel reads
 //     happening to produce this data are collapsed under that timestamp.
 message CommunicationComponentStateSnapshot {
-  // the UTC time when this snapshot was taken.
+  // The UTC time when the state was originally captured.
   google.protobuf.Timestamp snapshot_time = 1;
 
   // one or more high-level state codes active at snapshot_time.

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

@@ -475,7 +475,7 @@ message ElectricalComponentDiagnostic {
 
 // Representation of a component state, warnings, and errors.
 message ElectricalComponentStateSnapshot {
-  // The time at which the state was sampled.
+  // The UTC time when the state was originally captured.
   google.protobuf.Timestamp origin_time = 1;
 
 

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

@@ -169,7 +169,7 @@ message SensorDiagnostic {
 
 // Representation of a sensor state and errors.
 message SensorStateSnapshot {
-  // The time at which the state was sampled.
+  // The UTC time when the state was originally captured.
   google.protobuf.Timestamp origin_time = 1;
 
   // List of states of the microgrid sensor.