fix: MQTTAuth device lookup by Spec.DeviceID + PG15+ GRANT (v0.2.5)

- MQTTAuth: replaced Get(Name=deviceID) with List+filter by Spec.DeviceID
  (K8s object name != deviceID — caused deny for all devices)
- EnsureTenantDB: added GRANT role TO CURRENT_USER before CREATE DATABASE OWNER
  (PG15+ requires SET ROLE privileges for target owner)
- Image: naeel/iot-operator:v0.2.5
- E2E test passed: device create → MQTT publish → SQS → Postgres → REST API

deployments/k8s/iot-mqtt-bridge.yaml

@@ -38,7 +38,7 @@ spec:
         - name: mqtt-bridge
           # Тот же образ что и оператор — оба бинаря в одном слое (manager + iot-mqtt-bridge).
           # При смене версии оператора — менять тег и здесь.
-          image: naeel/iot-operator:v0.2.3
+          image: naeel/iot-operator:v0.2.5
           imagePullPolicy: Always
           command: ["/mqtt-bridge"]
           env:

deployments/k8s/iot-operator.yaml

@@ -3,7 +3,7 @@
 #
 # Компоненты:
 #   - ServiceAccount + ClusterRole + ClusterRoleBinding (RBAC для CRD controller)
-#   - Deployment: naeel/iot-operator:v0.2.3
+#   - Deployment: naeel/iot-operator:v0.2.5
 #   - Service: ClusterIP :9090 (REST API, MQTT auth/acl, admin UI)
 #
 # iot-operator обслуживает:
@@ -85,7 +85,7 @@ spec:
       serviceAccountName: iot-operator
       containers:
         - name: operator
-          image: naeel/iot-operator:v0.2.3
+          image: naeel/iot-operator:v0.2.5
           imagePullPolicy: Always
           ports:
             - name: api

deployments/k8s/iot-sqs-consumer.yaml

@@ -36,7 +36,7 @@ spec:
       containers:
         - name: sqs-consumer
           # Тот же образ что и оператор — все IoT бинари в одном образе.
-          image: naeel/iot-operator:v0.2.3
+          image: naeel/iot-operator:v0.2.5
           imagePullPolicy: Always
           command: ["/sqs-consumer"]
           env: