fix: move esbuild to devDependencies

[frenzzy]

Summary

• Move esbuild from dependencies to devDependencies in packages/start/package.json

Motivation

esbuild is only imported in build-time Vite plugin code (src/config/fs-routes/router.ts) and is never used by the production server output (.output/server/). Having it in dependencies causes:

1. Docker image bloat: esbuild ships a platform-specific Go binary (~9 MB) that gets installed even with npm ci --omit=dev
2. False-positive security findings: Security scanners (e.g., Trivy) flag Go stdlib CVEs in the esbuild binary that are not exploitable at runtime

Since vite (which itself depends on esbuild) is already a peerDependency, esbuild will always be available during the build step.

Closes #2135

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1b5b65e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for solid-start-landing-page ready!

Name	Link
🔨 Latest commit	1b5b65e
🔍 Latest deploy log	https://app.netlify.com/projects/solid-start-landing-page/deploys/69db52fb3e52ec000896d6eb
😎 Deploy Preview	https://deploy-preview-2136--solid-start-landing-page.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.