chore: add support for --provenance in pnpm publish

[remyleone]

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Relates OR Closes #0000

Release note for CHANGELOG:

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 50.78%. Comparing base (68a9cb3) to head (6ffb99b).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5656   +/-   ##
=======================================
  Coverage   50.78%   50.78%           
=======================================
  Files         340      340           
  Lines       77934    77934           
=======================================
  Hits        39577    39577           
  Misses      36861    36861           
  Partials     1496     1496           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR updates the release GitHub Actions workflow to publish the wasm npm package with provenance enabled, leveraging GitHub Actions OIDC to attach supply-chain provenance to published artifacts.

Changes:

• Add --provenance to the pnpm publish step in the release workflow to enable provenance during npm publishing.

---

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