chore: write the bin path the way npm publishes it

[kkdev92]

Writes the bin path the way npm publishes it, so the release log stops warning. The published package does not change.

Why

Every release logs:

npm warn publish npm auto-corrected some errors in your package.json when publishing.  Please run "npm pkg fix" to address these errors.
npm warn publish errors corrected:
npm warn publish "bin[vscode-ext-kit]" script name bin/vscode-ext-kit.mjs was invalid and removed

package.json wrote the entry as ./bin/vscode-ext-kit.mjs, and npm normalises it before publishing. The registry already has bin/vscode-ext-kit.mjs (npm view @kkdev92/vscode-ext-kit bin), so the published command was always right.

What changed

bin["vscode-ext-kit"]: ./bin/vscode-ext-kit.mjs → bin/vscode-ext-kit.mjs. This is exactly what npm pkg fix changes, and the only thing it changes (run on a copy of package.json).

Verification

• Nothing in scripts/, tests/ or src/ refers to the path string.
• CI's package job packs the tarball, installs it into a throwaway consumer and runs the checks in verify-package.mjs against it.

🤖 Generated with Claude Code