REPLY-51261: migrate release pipeline to semantic-release

[vigubikReply]

Replaces the bespoke internal build/publish scripts with semantic-release.

• Internal (automatic): merge to main -> publish to GitHub Packages @latest, tag vX.Y.Z, pre-release GitHub Release. Changelog lives in GitHub Releases.
• Versioning: Option B — package.json stays 0.0.0-development; CI never commits to main (only pushes tags). Seeded baseline tag v0.2.0 -> first feat: merge publishes 0.3.0.
• P1 fixed: publish gated on the full test matrix (ubuntu + windows) via the ci-ok gate job; a Windows-only failure blocks both merge and publish.
• Docs: README/docs/**-only changes skip the build and never publish.
• Commit guard: commitlint (husky commit-msg hook + PR check) since versioning derives from commit messages.
• Removed: old build.yml (@next) + internal release.yml (@next->@latest promotion).
• Deferred (not built): public-npm release — manual, tag-selected, gated on npm-name ownership.

Follow-up: require ci-ok + commitlint as status checks on main (branch protection) once these checks post here.

Ref: REPLY-51261