fix(release): add missing nodes package to release workflow

[bo-hyeon]

What does this PR do?

Adds the missing nodes package to the release workflow.

@pascal-app/nodes was split out into its own package but never added
to this workflow's package choice list or publish steps, so it has
never been publishable to npm — that's the root cause of npm-only
installs rendering nothing on 0.9.x (empty nodeRegistry).

This mirrors the existing core/viewer pattern: adds nodes to every
loop that iterates packages, and adds a "Build & publish nodes" step.

Fixes #454

---

Note

Low Risk
CI/release workflow only; no runtime or application code changes.

Overview
Wires @pascal-app/nodes into the manual release workflow so it can be version-bumped, built, and published like the other packages.

The workflow dispatch package choice now includes nodes, and every shell loop that bumps versions and syncs @pascal-app/* peerDependencies / devDependencies treats nodes the same as core, viewer, editor, mcp, and ifc-converter. A new Build & publish nodes step runs bun run build in packages/nodes and publishes with dry-run support, and the commit/tag step records NODES_VERSION when that package is released.

This closes the gap where the split-out nodes package was never on npm—matching the PR’s link to empty nodeRegistry on npm-only 0.9.x installs.

^{Reviewed by Cursor Bugbot for commit ee0a4df. Bugbot is set up for automated code reviews on this repo. Configure here.}