Rename category type field in ElectricalComponent

This commit renames the folowing:
- `ComponentCatgoryMetadataVariant` to
  `ElectricalComponentCategorySpecificInfo`
- `ElectricalComponent.category_type` to
  `ElectricalComponent.category_specific_info`

These renames make the entity names better reflect their purpose.

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

Author: tiyash-basu-frequenz

RELEASE_NOTES.md

@@ -22,6 +22,8 @@
 - Added new message `CommunicationComponentDiagnostic` to represent warnings and errors in microgrid communication components.
 - Added new message `CommunicationComponentStateSnapshot` to represent the state of communication components.
 - Added new message definitions for streaming events (Deleted, Created, Updated)
+- Renamed `ComponentCatgoryMetadataVariant` to `ElectricalComponentCategorySpecificInfo`.
+- Renamed field `ElectricalComponent.category_type` to `ElectricalComponent.category_specific_info` to better reflect its purpose.
 
 ## Bug Fixes
 

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

@@ -319,8 +319,8 @@ message MetricConfigBounds {
 }
 
 // Metadata specific to a microgrid component.
-message ElectricalComponentCategoryMetadataVariant {
-  oneof metadata {
+message ElectricalComponentCategorySpecificInfo {
+  oneof info {
     frequenz.api.common.v1.microgrid.electrical_components.Battery battery = 1;
     frequenz.api.common.v1.microgrid.electrical_components.EvCharger
       ev_charger = 2;
@@ -349,7 +349,7 @@ message ElectricalComponent {
   ElectricalComponentCategory category = 4;
 
   // The metadata specific to the component category type.
-  ElectricalComponentCategoryMetadataVariant category_type = 5;
+  ElectricalComponentCategorySpecificInfo category_specific_info = 5;
 
   // The component manufacturer.
   string manufacturer = 6;