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/build-manifest.json

@@ -0,0 +1,22 @@
+{
+  "pages": {
+    "/_app": []
+  },
+  "devFiles": [],
+  "polyfillFiles": [
+    "static/chunks/03~yq9q893hmn.js"
+  ],
+  "lowPriorityFiles": [
+    "static/Erg3te-xsOHqlolgOFE_K/_buildManifest.js",
+    "static/Erg3te-xsOHqlolgOFE_K/_ssgManifest.js",
+    "static/Erg3te-xsOHqlolgOFE_K/_clientMiddlewareManifest.js"
+  ],
+  "rootMainFiles": [
+    "static/chunks/098a0lm-b~rn..js",
+    "static/chunks/0tldj~reb5~dn.js",
+    "static/chunks/110q6k5sdl4es.js",
+    "static/chunks/14_678uuyq.tf.js",
+    "static/chunks/07uz2g0_38qia.js",
+    "static/chunks/turbopack-11jn_eqn~72wc.js"
+  ]
+}