Upgrade frigate-notify from v0.3.5 to v0.5.4 (#241)

## Summary
- Service review: upgrade frigate-notify from v0.3.5 to v0.5.4
- No breaking changes for current MQTT + ntfy config
- Notable additions: high-res snapshots, MQTT topic parsing fixes, env var parsing fixes

## Deployment and Testing
- [ ] Sync frigate app on ringtail: `argocd app set frigate --revision review/frigate-notify-v0.5.4 && argocd app sync frigate`
- [ ] Verify pod starts cleanly: `kubectl --context=k3s-ringtail -n frigate get pods`
- [ ] Trigger a test alert (motion event) and confirm ntfy notification arrives
- [ ] After merge: `argocd app set frigate --revision main && argocd app sync frigate`

Reviewed-on: https://forge.ops.eblu.me/eblume/blumeops/pulls/241

argocd/manifests/frigate/configmap-notify.yaml

@@ -10,7 +10,7 @@ data:
       public_url: https://nvr.ops.eblu.me
 
       webapi:
-        enabled: false
+        enabled: true
 
       mqtt:
         enabled: true

argocd/manifests/frigate/deployment-notify.yaml

@@ -16,7 +16,7 @@ spec:
     spec:
       containers:
         - name: frigate-notify
-          image: ghcr.io/0x2142/frigate-notify:v0.3.5
+          image: ghcr.io/0x2142/frigate-notify:v0.5.4
           env:
             - name: TZ
               value: America/Los_Angeles

docs/changelog.d/review-frigate-notify-v0.5.4.infra.md

@@ -0,0 +1 @@
+Upgrade frigate-notify from v0.3.5 to v0.5.4

service-versions.yaml

@@ -66,8 +66,8 @@ services:
 
   - name: frigate-notify
     type: argocd
-    last-reviewed: null
-    current-version: null
+    last-reviewed: 2026-02-22
+    current-version: "v0.5.4"
     upstream-source: https://github.com/0x2142/frigate-notify/releases
 
   - name: alloy-k8s