chore: set the package version to 0.3.0 for the release tag

[lmcorbalan]

Summary

No related issue. RUNBOOK.md step 2 of cutting a release: the root package.json's version is the npm package's, nothing checks it against the tag, and it has to land on main before v0.3.0 is pushed or consumers install a package whose manifest names a version their pin does not.

Changes

• Root package.json and package-lock.json to 0.3.0. No dependency, script or manifest field otherwise changed.

Acceptance criteria

• The version is the tag without its v, and nothing else in either manifest moved.

Test plan

Automated tests

check:deps, a clean npm ci (which runs prepare) and smoke:registry all exit 0; the packed tarball is now bootnodedev-canton-token-forge-0.3.0.tgz and installs, serves and shuts down in the scratch consumer.

Manual verification

npm version reformats the compact engines, bin and files objects, so the version was applied by hand and the diff is four lines across the two files.

Breaking changes

None.

Checklist

• Self-reviewed my own diff
• Tests added or updated
• Docs updated (if applicable)
• No unrelated changes bundled in

Screenshots

None.