chore: rename npm package from @bootnodedev/cbn to @bootnodedev/canton-barebones

[nicosampler]

Summary

No related issue. The npm package was published as @bootnodedev/cbn for early
npm testing; now that the repository is BootNodeDev/canton-barebones, the
package name moves to @bootnodedev/canton-barebones so the package, binary,
and repository all share one name.

Changes

• Rename the package to @bootnodedev/canton-barebones in package.json and regenerate package-lock.json
• Update the release workflow header comment and the CHANGELOG.md title to the new name
• Rename the temp-dir prefix in scripts/runtime-plan.test.js from cbn- to canton-barebones-
• Add a patch changeset documenting the rename

Acceptance criteria

• npm test and npx changeset status pass with the new package name
• No references to @bootnodedev/cbn remain outside CHANGELOG.md history entries
• After merge, @bootnodedev/canton-barebones is published to npm and @bootnodedev/cbn is deprecated (manual npm steps)

Test plan

Automated tests

npm test — full unit suite passes. scripts/runtime-plan.test.js was touched (temp-dir prefix only); no new tests were added since this change is metadata-only.

Manual verification

npx changeset status --since=origin/main reports a pending patch for @bootnodedev/canton-barebones.

Breaking changes

The npm package name changes: @bootnodedev/cbn will be deprecated and receive no further releases. Consumers must install @bootnodedev/canton-barebones instead. The CLI binary name (canton-barebones) is unchanged.

Checklist

• Self-reviewed my own diff
• Tests added or updated
• Docs updated (if applicable)
• No unrelated changes bundled in

Screenshots

None.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.