Play Framework

fix(skel): approve esbuild's build script for pnpm 11

The pnpm 10.34.5 -> 11.24.0 bump merged in the previous commit breaks
the Nuxt skel on its own. pnpm 11 promoted an unapproved dependency
build script from a warning to a hard error -- ERR_PNPM_IGNORED_BUILDS,
exit 1 -- and `pnpm run` reaches it through the implicit deps-status
install it performs before running a script. esbuild arrives
transitively via Nuxt's Vite build and has never been approved here,
so `pnpm run generate` failed before Nuxt even started.

Isolated with a control build: the same skel copy on pnpm 10.34.5 only
warns and prerenders all 4 routes, while 11.24.0 exits 1 during the
implicit install. Only the pnpm major differed.

The setting has to live in pnpm-workspace.yaml -- pnpm 11 ignores a
`pnpm` key in package.json -- and is spelled `allowBuilds`, not the
`onlyBuiltDependencies` that pnpm 10 used. pnpm 11 auto-migrates the
old key and rewrites the file with a `set this to true or false`
placeholder, which is how the rename surfaced.

Verified on the merged skel: pnpm 11.24.0 installs clean with no
ignored-builds error and `pnpm run generate` prerenders 4 routes.
pnpm 10.34.5 also still builds green against this file -- it ignores
the unknown key -- so a user whose corepack is not honouring
packageManager is not broken by it.

The file reaches scaffolded apps: setupNuxtFrontend in build.gradle.kts
copies the skel with an unfiltered walkTopDown(), and the placeholder
substitution pass leaves it byte-identical since it carries no
%APPLICATION_*% tokens.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>