Fix npm release tarball publishing

[manix84]

This pull request makes a minor version bump to the package and updates the npm publish commands to use a relative path with a leading ./ for the tarball file. This change ensures that the publish commands are more robust and compatible with npm's expected file path format.

Most important changes:

Version bump:

• package.json: Bumped the package version from 4.5.1 to 4.5.2.

Documentation updates:

• RELEASE.md: Updated all npm publish commands to use ./release-artifacts/arcade-engine-X.Y.Z.tgz instead of release-artifacts/arcade-engine-X.Y.Z.tgz. [1] [2]

Workflow update:

• .github/workflows/npm-release.yml: Changed the publish step to use ./$tarball instead of $tarball for the file path.

[Copilot]

Pull request overview

This PR updates the release workflow and documentation to ensure npm publishes the generated release tarball reliably by using an explicit relative path (./...), and bumps the package version for the release.

Changes:

• Bump package version from 4.5.1 to 4.5.2 (and sync package-lock.json).
• Update npm publish tarball paths in RELEASE.md to use ./release-artifacts/....
• Update the GitHub Actions npm publish step to publish ./$tarball instead of $tarball.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated 2 comments.

File	Description
RELEASE.md	Updates documented npm publish commands to use an explicit ./-prefixed tarball path.
package.json	Version bump to 4.5.2.
package-lock.json	Lockfile version fields updated to match 4.5.2.
.github/workflows/npm-release.yml	Publishes the tarball using npm publish "./$tarball" ... for path robustness.