fix: restore CI release bump flow

[osolmaz]

Summary

• fix the release workflow so CI syncs to the latest published npm version and lets release-it perform the requested bump
• reset committed repo version metadata in package.json and package-lock.json to 0.1.0

Verification

• pnpm run format:check
• dry-run of the release flow in an isolated clone on branch main
  • synced package.json to npm latest (0.1.15)
  • ran pnpm exec release-it 0.1.16 --ci --dry-run
  • confirmed release-it performed the release path instead of returning No new version to release

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e3ef6909da

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Bump package metadata to target version before release-it

This step now syncs package.json only to LATEST, but never applies TARGET before invoking release-it; with this repo’s .release-it.json (npm.version is set to false), release-it will not rewrite package.json itself, so the publish step still attempts to publish the already-published version and the release job fails when npm rejects duplicate versions. This regression is introduced by removing the second npm version bump that previously advanced to the requested increment.

Useful? React with 👍 / 👎.