Use KRaft mode for Sandbox deployment

Adapted Kafka configuration properties to use single node
Kafka instance in KRaft mode based on bitnami/kafka chart version
^26.8.

deploy/src/main/sandbox/hono-values.yml

@@ -205,6 +205,7 @@ commandRouterService:
     limits:
       memory: "120Mi"
 
+# assumes bitnami/kafka chart version ^26.8
 kafka:
   ## @param logFlushIntervalMessages The number of messages to accept before forcing a flush of data to disk
   ##
@@ -224,39 +225,31 @@ kafka:
   ## @param logSegmentBytes The maximum size of a log segment file. When this size is reached a new log segment will be created
   ## 10MB
   logSegmentBytes: _10485760
-  auth:
-    tls:
-      type: "pem"
-      pemChainIncluded: true
-      existingSecrets:
-      - "sandbox-tls"
+  tls:
+    type: "PEM"
+    pemChainIncluded: true
+    existingSecret: "sandbox-tls"
   externalAccess:
+    enabled: true
     autoDiscovery:
       enabled: false
-    service:
-      type: "LoadBalancer"
-      loadBalancerIPs:
-      - "hono.eclipseprojects.io"
-      nodePorts: []
+    broker:
+      service:
+        type: "LoadBalancer"
+        loadBalancerIPs:
+        - "hono.eclipseprojects.io"
+        nodePorts: []
+    controller:
+      service:
+        type: "LoadBalancer"
+        loadBalancerIPs:
+        - "hono.eclipseprojects.io"
+        nodePorts: []
+
   serviceAccount:
     create: false
   rbac:
     create: false
-  heapOpts: "-Xms650M -Xmx650M"
-  resources:
-    requests:
-      cpu: "50m"
-      memory: "800Mi"
-    limits:
-      memory: "800Mi"
-  zookeeper:
-    heapSize: 300
-    resources:
-      requests:
-        cpu: "50m"
-        memory: "400Mi"
-      limits:
-        memory: "400Mi"
 
 jaegerBackendExample:
   enabled: false