chore: set npm package version to 0.0.4

[tkkhq]

Summary

Sets the npm package version to 0.0.4 (was the 0.0.0 placeholder) so @volcano.dev/cli can be bootstrap-published cleanly.

Why

0.0.4 is the latest stable GitHub Release with downloadable binaries, so:

• the admin's first manual publish is a plain npm publish — no npm version step needed (which would otherwise trip the prepublishOnly 0.0.0 guard, and npm version v0.0.4 would fail anyway since the v0.0.4 git tag already exists);
• the published package's postinstall resolves the v0.0.4 release assets (verified present).

CI still runs npm version <tag> from the release tag on every future release, so this value stays current automatically — committing 0.0.4 just makes the one-time bootstrap frictionless.

Bootstrap flow (after this merges)

npm publish            # token auth, scoped-public via publishConfig.access

Then configure the OIDC trusted publisher (org Kong, repo volcano-cli, workflow publish-cli.yml, allow npm publish) and drop continue-on-error from the publish step. Subsequent stable vX.Y.Z tags publish automatically.

Verification

• package.json valid; npm pack --dry-run → volcano.dev-cli-0.0.4.tgz (6 files)
• v0.0.4 release SHA256SUMS + binaries return 206 (downloadable)
• prepublishOnly 0.0.0 guard retained

[Copilot]

Pull request overview

This PR bumps the @volcano.dev/cli npm package version from the 0.0.0 placeholder to 0.0.4, the latest stable GitHub Release with downloadable binaries. This enables a frictionless one-time manual bootstrap publish (npm publish) without tripping the prepublishOnly 0.0.0 guard, after which CI (npm version <tag>) keeps the value current on every future release.

Changes:

• Set package.json version to 0.0.4 (was 0.0.0).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.