fix: inject linux-musl sharp binaries into build/ to fix 502 on Dokploy

build.sh runs npm run build on macOS, so only the host's sharp binary
(darwin-arm64) got traced into the standalone output. The container
runs node:20-alpine (Linux, musl libc), which cannot load that binary
- the server crashed at runtime, causing a 502 even though the docker
build itself succeeded.

npm pack can fetch another platform's prebuilt sharp/libvips tarballs
without an install-time OS check, so build.sh now pulls the
linux-musl x64 and arm64 builds directly into build/node_modules and
drops the now-unused host binary.

build/.next/server/app/air-freight.meta

@@ -0,0 +1,17 @@
+{
+  "status": 308,
+  "headers": {
+    "location": "/doormile-wings",
+    "x-nextjs-stale-time": "300",
+    "x-nextjs-prerender": "1",
+    "x-next-cache-tags": "_N_T_/layout,_N_T_/air-freight/layout,_N_T_/air-freight/page,_N_T_/air-freight"
+  },
+  "segmentPaths": [
+    "/_tree",
+    "/_full",
+    "/air-freight/__PAGE__",
+    "/air-freight",
+    "/_index",
+    "/_head"
+  ]
+}