Grow the bundled template library to 83 homelab apps (0.43.0)

The library shipped five templates. This adds 78 more, covering what
homelab lists and the self-hosted community actually run: media servers
and the *arr automation chain, DNS ad-blocking, reverse proxies, VPN,
SSO, monitoring and dashboards, files/backup, notes and wikis, home
automation, dev tooling, databases, local AI, finance and notifications.

Every template follows the existing shape — compose.yaml, .env.example,
template.json — with PUID/PGID/TZ/DATA_PATH/HTTP_PORT knobs and no
literal secrets: anything that must be set uses ${VAR:?...} so deploy
fails loudly instead of coming up with a default password. Six ship the
extra config file their app needs (prometheus.yml, Caddyfile,
mosquitto.conf, frigate config.yml, Authelia's two files,
zigbee2mqtt configuration.yaml), which the folder-copy pull already
carries into the new stack.

All 95 referenced images were verified pullable against their
registries. Default host ports were deconflicted so several templates
can be pulled side by side; the only remaining overlaps are between
services you would never run together anyway (two DNS blockers on 53,
three reverse proxies on 80/443).

The Templates page would have been an unusable 83-card grid, so it now
has a search box and tag filter chips, with the tags on each card
clickable to filter by.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Dk43rmEeRfYi5wsLDbmfyG

README.md

@@ -76,11 +76,15 @@ as intuitive as Dockge, as capable as Portainer for Compose workflows.
   (`/proc/net/tcp[6]`) and running container bindings, with a confirm dialog.
 - **Resource limits**: CPU/memory sliders in the editor → `deploy.resources.limits`.
 - **Template library**: each template is a ready-to-run **stack folder** in git
-  (`backend/templates/<slug>/` — `compose.yaml` + `.env.example` + `template.json`).
-  Bundled set: Jellyfin, Vaultwarden, Uptime-Kuma, Paperless-NGX, Gitea. "Pull"
-  copies the whole folder into a new stack (`.env.example` → `.env`) which you then
-  edit and deploy. Save any stack back as a custom template (stored under
-  `${DATA_DIR}/templates/`). Add your own by dropping a folder into the templates dir.
+  (`backend/templates/<slug>/` — `compose.yaml` + `.env.example` + `template.json`,
+  plus any extra config the app needs, e.g. `prometheus.yml` or a `Caddyfile`).
+  83 bundled homelab apps across media, *arr automation, networking, reverse
+  proxies, VPN, SSO, monitoring, dashboards, files/backup, notes and wikis, home
+  automation, dev tooling, databases, local AI and more — searchable and
+  filterable by tag on the Templates page. "Pull" copies the whole folder into a
+  new stack (`.env.example` → `.env`) which you then edit and deploy. Save any
+  stack back as a custom template (stored under `${DATA_DIR}/templates/`). Add
+  your own by dropping a folder into the templates dir.
 - **Healthcheck status** surfaced per container in the stack overview.
 
 ### Phase 4 — Operations