fix: migrate esbuild build approval to pnpm 11

[timelis]

Summary

• Migrate the esbuild build approval from the deprecated onlyBuiltDependencies setting to pnpm v11's allowBuilds configuration.
• Include pnpm-lock.yaml and pnpm-workspace.yaml in the Docker build context and image stages.
• Keep pnpm@latest instead of pinning the Docker build to an older pnpm release.

Root cause

A clean docker compose build currently fails in two stages:

1. .dockerignore excludes pnpm-lock.yaml, even though the Dockerfile copies it.
2. Once the lockfile is available, pnpm v11 rejects the unapproved esbuild@0.27.7 postinstall script with ERR_PNPM_IGNORED_BUILDS.

The existing .npmrc uses onlyBuiltDependencies, which is deprecated in pnpm v11. This change replaces it with the supported project-level configuration:

allowBuilds:
  esbuild: true

Changes

• Stop excluding pnpm-lock.yaml from the Docker build context.
• Replace .npmrc with pnpm-workspace.yaml and explicitly allow the esbuild build script.
• Copy pnpm-workspace.yaml into both Docker stages before dependency installation.

Validation

• docker compose build --no-cache
  • pnpm 11.13.1
  • esbuild postinstall completed successfully
  • both HTTP and stdio images built successfully
• docker compose up -d
  • both services started and reported healthy
• pnpm test: 25 tests passed
• pnpm run type-check: passed
• git diff --check: passed
• pnpm run lint: reports an existing formatting error in src/server.test.ts and an existing warning in src/utils/responseFormatter.ts; neither file is changed by this PR

Closes #59

Alternative to #60: this fixes the same Docker build failure by migrating the project configuration to pnpm v11 instead of pinning pnpm to v10.

Related core workflow workaround: Dokploy/dokploy#4839

[Siumauricio]

Thanks for the PR, @timelis — you correctly identified both problems breaking the Docker build from a fresh clone (the lockfile being excluded by .dockerignore and pnpm 10+ blocking esbuild's build script).

Closing this one because the build issue was resolved by merging #60, which took a slightly different approach: pinning pnpm@10.33.0 in the Dockerfile and copying the existing .npmrc (which already carries the esbuild build approval) into the image. That keeps the build reproducible without changing the repo's package-manager config.

The pnpm 11-style migration you propose here (pnpm-workspace.yaml with allowBuilds, dropping .npmrc) is a reasonable direction, but we'd rather do it as part of an intentional pnpm 11 upgrade for the whole project than as a side effect of the Docker fix. We'll keep it in mind for when that happens.

Thanks again for the contribution!