Make ClusterCapabilities fields optional during rollout

Author: lomidzemikheili

gen/go/qdrant/cloud/cluster/v1/cluster.pb.go

@@ -1064,7 +1064,8 @@ message ClusterState {
   // If enabled, you can generate JWT tokens with fine-grained rules for access control.
   bool jwt_rbac = 10;
   // Specifies whether some operations are supported by cluster or not.
-  ClusterCapabilities capabilities = 11 [(buf.validate.field).required = true];
+  // Optional during rollout; will become required once all producers populate it.
+  ClusterCapabilities capabilities = 11;
 }
 
 // ClusterNodeInfo represents a node in a cluster.
@@ -1214,12 +1215,15 @@ message ClusterBackupSupportInfo {
 message ClusterCapabilities {
   // Whether the StorageClass used by the cluster supports disk expansion or not.
   // Disk scaling will be enabled or disabled based on this for hybrid cloud clusters.
-  ClusterDiskExpansionSupportInfo disk_expansion = 1 [(buf.validate.field).required = true];
+  // Optional during rollout; will become required once all producers populate it.
+  ClusterDiskExpansionSupportInfo disk_expansion = 1;
   // Whether it is possible to take a backup for the cluster or not.
   // Backup tab will be shown or hidden based on this for hybrid cloud clusters.
-  ClusterBackupSupportInfo backup = 2 [(buf.validate.field).required = true];
+  // Optional during rollout; will become required once all producers populate it.
+  ClusterBackupSupportInfo backup = 2;
   // Whether the cluster can be scaled up or down.
-  ClusterScalabilityInfo scalability_info = 3 [(buf.validate.field).required = true];
+  // Optional during rollout; will become required once all producers populate it.
+  ClusterScalabilityInfo scalability_info = 3;
 }
 
 // buf:lint:ignore QDRANT_CLOUD_REQUIRED_ENTITY_FIELDS