chore: release neon@3.2.1, neonctl@3.2.1

[andrelandgraf]

Problem

neon init still installed the retired neonctl package (#432). That is on main and queued behind a pending changeset. npm still serves neon@3.2.0 / neonctl@3.2.0.

Release

• neon: 3.2.0 → 3.2.1
• neonctl: 3.2.0 → 3.2.1 (fixed-group compatibility package)

Consumes .changeset/init-install-neon-not-neonctl.md and writes the package changelogs. No source changes.

npm i -g neon
neon init

neon init now detects and installs the neon CLI. Version probing checks neon first (falling back to neonctl so an existing global install still counts), the update check reads npm view neon, and auth/context lookups shell out to neon.

Verification

• pnpm changeset version
• pnpm lint:ci
• Diff is the consumed changeset, two package.json versions, and two changelogs

Publish order

After merge: neon → neonctl.