fix(compute): use @prisma/cli@next commands that exist in the published Prisma 8 CLI

[ankur-arch]

What was broken

@prisma/cli@latest on npm resolves to 3.0.0-beta.30, an abandoned 2021 pre-release. The command groups app and database that the Compute scripts relied on do not exist in Prisma 8 (8.0.0-rc.1).

Command mapping

Old (broken)	New (8.0.0-rc.1)
bunx @prisma/cli@latest	bunx @prisma/cli@next
database create <name> --branch main	postgres create <name> --branch main
app deploy --env .env (compute:deploy script)	git connect → renamed to compute:connect; every push to the connected branch builds and deploys automatically
app open	service open
app logs	removed; build logs are available via npx -y @prisma/cli@next build logs <build-id> from the GitHub check run

When to flip back to @latest

When Prisma 8 reaches general availability, replace all @prisma/cli@next references with @prisma/cli@latest.

🤖 Generated with Claude Code

[ankur-arch]

Correction to this PR's framing (the change itself stands): @prisma/cli@latest is the current 3.x platform-CLI beta — the old scripts work today against it. This PR moves the example onto the Prisma 8 command set (@prisma/cli@next), which is what latest becomes at GA, when the app/database groups disappear.