301 Redirect Support for Unpublished Hospitable Subdomains

Unpublishing a Hospitable direct booking site removes the per-site route and static files. The subdomain falls through to a wildcard handler returning HTTP 200 with an empty body, which Google reads as a soft 404. Hosts who migrate to a custom domain lose any existing SEO authority built on their Hospitable subdomain, and old URLs de-index slowly without passing ranking signals. Request: Allow hosts to configure a 301 redirect from their unpublished Hospitable subdomain to a destination URL of their choice (e.g. their primary custom domain) either at the time of unpublishing or as a setting in the direct booking site configuration.