chore: release neon@4.5.0, neonctl@4.5.0

[andrelandgraf]

Problem

neon claim and its claimable alias are on main from #423, along with the Claimable Neon capability-error handling in Config-as-Code. Neither is on npm. npm latest is still neon@4.4.0 / neonctl@4.4.0, and npx neon@4.4.0 claim --help does not list create, so anyone following the claim flow against the published CLI hits a command that isn't there.

The pending changeset .changeset/calm-bears-claim.md is what blocks the release. Until it is consumed, no version exists to publish.

The change

changeset version run on main. The changeset file is deleted, package.json versions are bumped and each CHANGELOG.md gets the entry. No source files change.

Package	From	To	Why
neon	4.4.0	4.5.0	minor: neon claim / claimable
neonctl	4.4.0	4.5.0	fixed group with neon
@neon/config	1.0.2	1.0.3	patch: Claimable Neon capability errors
@neon/config-runtime	1.0.2	1.0.3	dependent of @neon/config
@neon/env	1.1.2	1.1.3	dependent of @neon/config
@neon-internals/env-core	0.0.2	0.0.3	dependent of @neon/config; private, never published

What users get on merge

The published neon gains the claim command group. From the changeset now in packages/cli/CHANGELOG.md:

neon claim
neon claimable   # alias

create, use, accept, list, status and delete. status, accept and delete take an optional project id from claim list. list prints state from the assertion clock plus the project expiry. delete drops a local record once the identity assertion has expired. create prints the CLI service names and project_expires_at.

neonctl behavior is unchanged; it moves to 4.5.0 only because it is versioned in a fixed group with neon.

For @neon/config, @neon/config-runtime and @neon/env callers, no exported signature changes. The @neon/config patch is the capability-error recognition from #423: an unavailable pre-claim service keeps its claim guidance instead of surfacing as an API-key failure.

Verification

• biome ci --error-on-warnings passed across 726 files.
• The version bumps and changelog entries in this diff are the output of the changesets tool, not hand-edited.

Not verified here: the neon claim behavior itself. That was exercised in #423 against the live service. This branch contains no code to exercise.

Nothing has been published from this branch. Release happens through the pipeline after merge, and npm latest should be checked for neon@4.5.0 and neonctl@4.5.0 once it completes.

For your attention

• @neon/config ships a patch that has nothing to do with claiming, from the same changeset. Add neon claim for temporary projects without an account #423 changed both, so they release together. Splitting them now would mean editing a consumed changeset.
• @neon-internals/env-core is bumped but private. The version move is bookkeeping inside the monorepo and no artifact leaves it.