[Docs] Add homelab deployment guide

[roomote-roomote]

Created by Roomote. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• add a homelab deployment guide centered on a full Proxmox VM, Tailscale administration, and a stable public HTTPS origin
• compare direct public DNS, Cloudflare Tunnel, and Tailscale Funnel ingress paths with their operational tradeoffs
• include a provider-agnostic prompt that a local agent can follow without collecting provider credentials or exposing the setup token
• add the guide to Getting Started and link it from the existing self-hosting page

Why this change was made

The existing self-hosting guide covers the installer and production stack, but homelab operators still need help choosing VM resources, private access, public ingress, DNS, and tunnel behavior. This gives them an actionable path without duplicating the supported installer.

Impact

Homelab users can deploy Roomote with clearer infrastructure boundaries, understand why Tailscale complements rather than replaces public ingress, and hand safe host preparation steps to a local coding agent. The upstream Proxmox community helper script remains a separate follow-up and is not required by this guide.

[roomote-community]

No new code issues found. See task

• apps/docs/homelab.mdx:111 The public-DNS installer command, and the equivalent Cloudflare command at line 127, pipe into an unprivileged bash. deploy/install.sh exits unless it runs as root, so following either new primary setup path from a normal SSH account fails before installation. Pipe to sudo bash -s -- (or explicitly require a root shell).

_{Reviewed 15252f7}

[roomote-roomote]

Fixed the outstanding installer-permissions feedback in 15252f7: both homelab installer examples now pipe through sudo bash -s --, matching the installer's root requirement. The docs validation and broken-link checks pass.