fix(home-assistant-mcp): use RollingUpdate and allow image.tag override

Recreate strategy caused full downtime when a chart appVersion bump
referenced an unpublished image tag. Switch to RollingUpdate with
maxUnavailable=0 so the old pod stays up until the new one is Running,
and add an image.tag override so consumers can pin to a working tag
when appVersion races ahead of the published image.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

home-assistant-mcp/Chart.yaml

@@ -2,7 +2,7 @@ apiVersion: v2
 name: home-assistant-mcp
 description: Home Assistant MCP server Helm chart
 type: application
-version: 0.2.3
+version: 0.3.0
 appVersion: "7.4.1"
 annotations:
   version-source: github-release:homeassistant-ai/ha-mcp

home-assistant-mcp/templates/deployment.yaml

@@ -14,7 +14,10 @@ metadata:
 spec:
   replicas: 1
   strategy:
-    type: Recreate
+    type: RollingUpdate
+    rollingUpdate:
+      maxUnavailable: 0
+      maxSurge: 1
   selector:
     matchLabels:
       app: {{ .Release.Name }}
@@ -33,7 +36,7 @@ spec:
       {{- end }}
       containers:
         - name: {{ .Chart.Name }}
-          image: "{{ .Values.image.repository }}:{{ .Chart.AppVersion }}"
+          image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
           imagePullPolicy: {{ .Values.image.pullPolicy }}
           {{- with .Values.command }}
           command: