Update pnpm `onlyBuiltDependencies` config

[hyunbinseo]

onlyBuiltDependencies in pnpm-workspace.yaml is supported from pnpm@10.5:

The pnpm.* settings from package.json can now be specified in the pnpm-workspace.yaml file instead.

onlyBuiltDependencies:
- esbuild
- fuse-native

pnpm approve-builds adds onlyBuiltDependencies to pnpm-workspace.yaml as of 10.7.1.

Current implementation is fixed to the pnpm.onlyBuiltDependencies field in the pacakge.json:

• feat: support pnpm version 10 #432

Backwards compatibility is supported and is probably fixed (?) in 10.6.1

When executing the approve-builds command, if package.json contains onlyBuiltDependencies or ignoredBuiltDependencies, the selected dependency package will continue to be written into package.json.

[manuel3108]

I wonder what should happen if there is no pnpm-workspace.yaml because you are creating a new project. Should it just be created to only add those three lines?

Basically I think this is a good idea, because it puts pnpm related stuff in an pnpm file

[hyunbinseo]

The pnpm-workspace.yaml seems to be created.

corepack use pnpm@latest
# Installing pnpm@10.7.1 in the project...

pnpm i @sveltejs/kit -D
# Ignored build scripts: esbuild.
# Run "pnpm approve-builds" to pick which dependencies should be allowed to run scripts.

pnpm approve-builds
# √ The next packages will now be built: esbuild.
# Do you approve? (y/N) · true -- workspace file is generated at this point.

# pnpm-workspace.yaml
onlyBuiltDependencies:
  - esbuild