Add Home Assistant to CrowdSec variants

Add Home Assistant (home-automation hub, port 8123) to the -crowdsec scripts
for 24.04 and 26.04, following the existing service pattern (menu entry,
detection, defaults, parse, uninstall, install block, UFW rule, Caddy template).

- Image ghcr.io/home-assistant/home-assistant:stable, config volume, privileged
  + /run/dbus for hardware integrations; documents host-networking alternative
  for full mDNS/device discovery.
- Pre-seeds config/configuration.yaml with default_config + http.trusted_proxies
  (only on a fresh install) so HA works behind the Caddy reverse proxy without
  the usual 400 'request from reverse proxy' error.
- Integrates with configure_caddy_for_service (subdomain 'home').

Added only to the -crowdsec tier (current tip); original and -no-keycloak
scripts stay frozen as the evolution record. Both variants pass 'bash -n' and a
--dry-run --unattended pass (exit 0), including with Home Assistant forced on.

https://claude.ai/code/session_017eA2qqq9jfF2tNtpUYL8vK

SCRIPT-VARIANTS.md

@@ -12,6 +12,13 @@ complete, standalone script).
 
 `<ver>` is `24.04` or `26.04`.
 
+> New services are added to the **`-crowdsec`** tier only (the current tip of
+> the evolution); the original and `-no-keycloak` scripts are frozen as
+> historical snapshots. For example, **Home Assistant** (home-automation hub,
+> port 8123) is available in the `-crowdsec` variants. It ships with a
+> `trusted_proxies` config pre-seeded so it works behind the Caddy reverse
+> proxy out of the box.
+
 ## Which one?
 
 - **Original (`.sh`)** — unchanged baseline, kept for fallback. Still offers