Fix pnpm installs in cf init Worker projects

[penalosa]

Summary

• Generate pnpm-workspace.yaml for new Worker projects when pnpm is selected, approving the esbuild and workerd build scripts before installation.
• Keep the approvals in projects created with --no-install so a later pnpm install works.
• Cover the generated file and its timing in the cf init tests, and add a patch changeset.

This applies the build approval policy from cloudflare/workers-sdk#14193 to the cf init scaffold.

Validation

• pnpm test src/__tests__/commands/init.test.ts (27 passed)
• pnpm --filter cf check:type
• pnpm check:lint
• pnpm exec oxfmt --check on changed files

Closes #92

[pkg-pr-new]

npm i https://pkg.pr.new/cf@136

commit: e3a9d5f

[ask-bonk]

LGTM

github run

[github-actions]

cf --help startup

	mean	stddev	min	max
PR	329.4 ms	4.3 ms	323.7 ms	342.1 ms
base	331.7 ms	8.1 ms	324.8 ms	359.0 ms

Δ (PR vs base): ↓ -2.3 ms (-0.7%)

Measured with hyperfine on ubuntu-latest (3 warmup runs, 20 timed runs). CI numbers carry ±a few ms of runner jitter; treat small deltas as noise.

[petebacondarwin]

NIT: I'd update the helper to make the tests cleaner when we don't care about the pm in use.

Also, when running cf init in an existing directory, I think we delegate to auto-config. Does this already handle adding in this workspace directory?

[ask-bonk]

LGTM

github run