Fix npm trusted publishing release runner

[suguanYang]

Summary

• update the release workflow from Node 22.12.0 to 22.14.0 for both stable and beta publish jobs
• keep workflow/script-only PRs from requiring a package changeset, so release-tooling fixes can merge without creating a fake SDK version bump
• remove the stale private-repository provenance comment from the stable publish script

Why

The merged 0.6.0 release PR (#89) failed during npm publish; npm still reports @ontos-ai/knowhere-sdk latest as 0.5.0. The release workflow already grants id-token: write and installs npm 11.5.2+, but npm trusted publishing currently requires Node 22.14.0+.

This PR makes the repo-side release runner compatible with npm trusted publishing so merging it should let the next main-branch Release Management run publish the already-versioned 0.6.0 package. If npm trusted publishing is not configured for this package/workflow, the remaining blocker is npm package settings or the npm token's org/package permissions.

Official npm docs: https://docs.npmjs.com/trusted-publishers/

Verification

• npm ci
• npm run release:check-changeset -- origin/main
• npm run format:check
• npm run typecheck
• npm run lint
• npm run test:ci
• npm run build
• git diff --check