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/favicon.ico/route.js

@@ -0,0 +1,6 @@
+var R=require("../../chunks/[turbopack]_runtime.js")("server/app/favicon.ico/route.js")
+R.c("server/chunks/[root-of-the-server]__009pdeo._.js")
+R.c("server/chunks/[root-of-the-server]__0j8-xkl._.js")
+R.c("server/chunks/_next-internal_server_app_favicon_ico_route_actions_095lj93.js")
+R.m(88165)
+module.exports=R.m(88165).exports

build/.next/server/app/favicon.ico/route.js.map

@@ -0,0 +1,5 @@
+{
+  "version": 3,
+  "sources": [],
+  "sections": []
+}

build/.next/server/app/favicon.ico/route/app-paths-manifest.json

@@ -0,0 +1,3 @@
+{
+  "/favicon.ico/route": "app/favicon.ico/route.js"
+}

build/.next/server/app/favicon.ico/route/build-manifest.json

@@ -0,0 +1,9 @@
+{
+  "devFiles": [],
+  "ampDevFiles": [],
+  "polyfillFiles": [],
+  "lowPriorityFiles": [],
+  "rootMainFiles": [],
+  "pages": {},
+  "ampFirstPages": []
+}