fix(next): run eve dev server with node under bun

[zjy365]

Summary

• start the withEve sidecar dev server with Node when the host Next.js process is running under Bun
• add regression coverage for Bun-hosted Next.js dev startup
• add a patch changeset

Why

When a Next.js app is launched with bun --bun next dev, process.execPath points at Bun. withEve used that executable to spawn the local eve dev --no-ui --port 0 server, which let Bun runtime globals leak into the Nitro worker and caused crossws to reject the Node adapter.

Verification

• corepack pnpm --filter eve run build:js
• corepack pnpm --filter eve exec vitest run --config vitest.integration.config.ts src/public/next/server.integration.test.ts
• corepack pnpm --filter eve run typecheck
• corepack pnpm exec oxlint packages/eve/src/public/next/server.ts packages/eve/src/public/next/server.integration.test.ts
• git diff --check

Closes #101

[vercel]

@zjy365 is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.