feat(tanstack-start): add dedicated build adapter

[tensordreams]

Linked issue

Closes #118

Summary

Add a first-party TanStack Start build adapter to Composer. The authoring surface is tanstackStart({ module, appDir }), and deploy configuration registers tanstackStartBuild() from @prisma/composer/tanstack-start/control.

The control adapter reads .output/nitro.json, requires the Nitro node-server preset, takes the authoritative serverEntry from the manifest, and delegates the complete output-tree assembly to the existing Node directory adapter. This preserves server chunks and client/public assets without hardcoding the emitted entry path.

The runnable TanStack Start example and both public guidance surfaces now use the dedicated adapter.

Testing performed

• pnpm build
• pnpm typecheck
• pnpm lint
• pnpm test
• pnpm lint:deps
• pnpm lint:rules:symlinks
• pnpm check:publish-deps
• The example integration test assembles the Nitro output, boots the assembled server entry, verifies SSR, and fetches a copied public asset.

Checklist

• All commits are signed off (git commit -s) per the DCO. The DCO status check will block merge if any commit is missing a Signed-off-by: trailer.
• I read CONTRIBUTING.md and the change is scoped to one logical concern.
• The PR title is a conventional commit (feat, fix, chore, docs, refactor, test, build) — PR titles drive the auto-generated release notes.
• Tests are updated (or n/a if the change is doc-only / refactor with no behavioural delta).

Notes for the reviewer

Build execution remains user-owned per ADR-0005: run vite build before deploy. The dedicated adapter interprets only the stable Nitro build manifest needed to assemble its already-built runnable output.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@prisma/composer@119

npm i https://pkg.pr.new/@prisma/composer-prisma-cloud@119

commit: de3cead

[aqrln]

Isn't it the whole point of Composer to run these things for you automatically? Also, why does our in-app-tree version have a dedicated tanStackStartBuild() but this version use vanilla nodeBuild()?