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-common.sh

@@ -349,6 +349,12 @@ pull_prod_release_images() {
   require_release_image
   ensure_registry_transport_configured
 
+  local release_image="${APP_IMAGE:-rentaldrivego/carmanagement}:${IMAGE_TAG}"
+  if [[ "${IMAGE_TAG}" != "latest" ]] && docker image inspect "${release_image}" >/dev/null 2>&1; then
+    echo "Release image ${release_image} is already present locally; skipping docker pull."
+    return 0
+  fi
+
   if load_release_image_archives; then
     return 0
   fi
@@ -360,7 +366,7 @@ pull_prod_release_images() {
     exit 1
   fi
 
-  prod_compose pull migrate api carplace dashboard admin
+  prod_compose pull migrate api homepage carplace dashboard admin
 }
 
 load_release_image_archives() {