[CP-410] BREAKING: Removed deprecated DatabaseConfigurationService.jwt_rbac (#276)

Breaking info
```
proto/qdrant/cloud/cluster/v1/cluster.proto:787:1:Previously present field "3" with name "jwt_rbac" on message "DatabaseConfigurationService" was deleted.
⚠️  Warning: Breaking changes detected! These should generally be avoided. Continuing with code generation...
```

Author: Robert-Stam

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

@@ -795,14 +795,8 @@ message DatabaseConfigurationService {
   // If set, all requests must include a header with the api-key.
   // example header: `api-key: <API-KEY>`
   optional common.v1.SecretKeyRef read_only_api_key = 2;
-  // Enable JWT Role Based Access Control (RBAC).
-  // This setting is for both managed and hybrid cloud clusters.
-  // For managed cloud clusters, this defaults to enabled and cannot be explicitly disabled.
-  // For hybrid cloud clusters, the value is applied as provided.
-  // If enabled, you can generate JWT tokens with fine-grained rules for access control.
-  // Use generated token instead of API key.
-  // Deprecated: use cluster.status.jwt_rbac instead to read and ClusterService.EnableClusterJwtRbac to change the state.
-  optional bool jwt_rbac = 3 [deprecated = true];
+  // Previously: optional bool jwt_rbac.
+  reserved 3;
   // Enable HTTPS for the REST and gRPC API
   // This setting is for hybrid cloud clusters only, for managed cloud clusters the platform controls it (and clients need to use a secure connection).
   optional bool enable_tls = 4;