infra: publish releases with provenance

[ST-DDT]

This PR adds release providence to our releases on npm.

Example:

I haven't tested the pipeline changes myself, but I verified with various other libraries, that the syntax should work.

I decided to use an ENV variable to set the flag as I consider it easier to read than the other alternatives (--flag, .npmrc).
Also it does not prevent publishing from our own computers, if ever needed again.

Example projects

• nuxt/nuxt@ec15037
• toeverything/blocksuite@b6cb911
• https://github.com/vitest-dev/vitest/blob/main/.github/workflows/publish.yml#L10 + vitest-dev/vitest@0882460

See also

• https://github.com/npm/provenance
• https://docs.npmjs.com/cli/v10/commands/npm-publish#provenance

[netlify]

✅ Deploy Preview for fakerjs ready!

Name	Link
🔨 Latest commit	7bf7119
🔍 Latest deploy log	https://app.netlify.com/sites/fakerjs/deploys/66e966a7f8c50c000860cdcb
😎 Deploy Preview	https://deploy-preview-3119.fakerjs.dev
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.97%. Comparing base (48f171e) to head (7bf7119).
Report is 1 commits behind head on next.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #3119      +/-   ##
==========================================
- Coverage   99.97%   99.97%   -0.01%     
==========================================
  Files        2776     2776              
  Lines      226338   226338              
  Branches      944      943       -1     
==========================================
- Hits       226285   226274      -11     
- Misses         53       64      +11     

see 1 file with indirect coverage changes

[Shinigami92]

Cool