Fix Default template dependency installation

[pabloelisseo]

Root cause

The starter previously pinned pnpm 10.14.0 through its packageManager field, but that field was lost during an upstream template sync. Without the pin, fresh Fusion containers let Corepack select the latest pnpm release, currently 12.3.4. Fusion’s Node 22.22.0 image bundles Corepack 0.34.0, which tries to launch pnpm from bin/pnpm.cjs; pnpm 12 no longer ships that entrypoint, so project setup fails before dependency installation with MODULE_NOT_FOUND.

Summary

• pin generated Fusion starter projects to pnpm 10.14.0
• prevent Node 22.22.0's bundled Corepack from selecting incompatible pnpm 12
• refresh existing idempotence targets for the latest upstream data-storage guide wording

Verification

• applied the starter patch to pristine and previously patched trees
• verified a second patch application produces no changes
• verified node:22.22.0 resolves pnpm 10.14.0 from the generated manifest
• installed generated starter dependencies successfully
• ran the generated starter typecheck

The generated starter build still encounters the existing ignored better-sqlite3 native build-script issue after dependency installation; this change is limited to restoring the working package-manager bootstrap.