Fix production deployment for public site routing

- pass `NEXT_PUBLIC_CARPLACE_URL` into the production Docker build
- keep `NEXT_PUBLIC_STOREFRONT_URL` as a backward-compatible fallback
- run the production deploy script from the Gitea workflow after building
- include `homepage` in production deploy, pull, and health-check service lists
- allow deploy to use a release image already built locally on the VPS

scripts/docker-prod-run-pulled-image.sh

@@ -90,7 +90,7 @@ echo "Applying migrations"
 prod_compose run --rm migrate
 
 echo "Starting application services"
-app_services=(api carplace dashboard admin)
+app_services=(api homepage carplace dashboard admin)
 
 if [[ "${INCLUDE_PGMANAGE}" == "1" ]]; then
   prod_compose --profile private-tools up -d "${app_services[@]}" pgmanage
@@ -98,6 +98,7 @@ else
   prod_compose up -d "${app_services[@]}"
 fi
 wait_for_healthy api 180
+wait_for_healthy homepage 180
 wait_for_healthy carplace 180
 wait_for_healthy dashboard 180
 wait_for_healthy admin 180