feat(publish): add npm provenance to lerna publish

[ghiscoding]

Description

As per Lerna PR 3674

This will provide access to npm provenance with GitHub Actions https://github.blog/2023-04-19-introducing-npm-package-provenance/

Motivation and Context

As per Lerna PR 3674, this follows Lerna implementation

Provenance is now fully supported when publishing with lerna as of v6.6.2

All of these methods (from https://docs.npmjs.com/generating-provenance-statements#using-third-party-package-publishing-tools) of letting lerna know about provenance are supported, so choose the one that works best for you:

Here is a real example published with lerna:

NOTE: Provenance is currently only supported by npm for Github Actions

How Has This Been Tested?

Types of changes

• Chore (change that has absolutely no effect on users)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[codecov]

Codecov Report

Merging #600 (11a5ceb) into main (b043c78) will decrease coverage by 0.09%.
The diff coverage is 59.26%.

@@            Coverage Diff             @@
##             main     #600      +/-   ##
==========================================
- Coverage   98.18%   98.09%   -0.09%     
==========================================
  Files         152      152              
  Lines       11465    11491      +26     
  Branches     1880     1881       +1     
==========================================
+ Hits        11256    11271      +15     
- Misses        208      219      +11     
  Partials        1        1              

Impacted Files	Coverage Δ
packages/publish/src/publish-command.ts	98.25% <59.26%> (-1.05%)	⬇️