chore(release): prepare 0.2.0

[moonyue-w]

Summary

Prepare the TypeScript SDK for 0.2.0: synchronize package.json, both root versions in package-lock.json, and src/version.ts; regenerate the API reference for VERSION; and move the reviewed changes into the dated 0.2.0 changelog entry. Keep an empty Unreleased section and preserve all breaking-change migration guidance and 0.1.0 history.

Why

The release workflow requires all package/runtime versions and a nonempty changelog entry to match the requested release. The minor-version bump follows the pre-1.0 compatibility policy for the error hierarchy and pagination changes already merged into main.

Verification

• npm run build (also exercised by tests and packaging)
• npm run typecheck
• npm test: 3,375 passed on Node 22.22.2.
• npm run docs:check: passed; 26 README TypeScript snippets compiled.
• npm pack: confirmed tarball metadata and CommonJS/ESM runtime versions report 0.2.0.
• Changelog validation and extraction for 0.2.0; 19 release-notes automation tests passed.
• Standalone examples were not rerun; example source is unchanged and README snippets were typechecked.
• Account-backed integration tests are not required for this version/documentation-only PR; the source baseline passed integration before the version bump.

Impact

• Version metadata and the generated VERSION reference are updated; no new API or behavioral changes are introduced here.
• Reviewed user-facing notes moved from Unreleased to 0.2.0 without alteration, including error handling and pagination migration guidance.
• CommonJS, ESM, and subpath exports remain covered by build/type tests; contract and wire-field fixtures are unchanged.
• Go and Python release versions are coordinated at 0.2.0.
• No credentials, environment files, logs, or generated test output committed.