fix(ci): replace sed version bump with npm version to prevent script corruption

[Kyzgor]

Summary

Replace the greedy sed regex in the CI publish workflow with npm version, and restore the corrupted version script in package.json.

Problem

The CI workflow (node_sdk_publish.yaml) uses sed -i "s/\"version\": \".*\"/.../" to bump the version before publishing. This regex matches every "version": "..." pattern in package.json — not just the top-level version field, but also the version script inside scripts.

This caused the version script to be silently corrupted from "standard-version" to the release version string (e.g., "2.5.2"). The corruption was introduced in commit 2abe31f and has persisted since.

Solution

• Replace sed with npm version "$TAG" --no-git-tag-version --allow-same-version --ignore-scripts, which safely modifies only the top-level version field via npm's JSON-aware tooling
• --no-git-tag-version prevents npm from creating a git commit and tag
• --ignore-scripts prevents the version lifecycle script (standard-version) from running during the CI bump
• Restore the version script in package.json from the corrupted "2.5.2" back to its original value: "standard-version"

Changes

• .github/workflows/node_sdk_publish.yaml — replaced sed command with npm version
• package.json — restored scripts.version from "2.5.2" to "standard-version"

Testing

Verified locally that npm version "X.Y.Z" --no-git-tag-version --allow-same-version --ignore-scripts:

• Correctly updates only the top-level version field
• Does not modify scripts.version
• Does not trigger lifecycle scripts, create commits, tags, or changelogs

Backwards Compatibility

No breaking changes. The npm version command produces the same result (updated version field) without the side effect of corrupting other fields.

Fixes #89