ci: add npm provenance

[NachoVazquez]

By submitting this pull request, I confirm that my contribution is made under the terms of the MIT license.

Problem/Feature

We are not generating NPM provenance when releasing to NPM.

https://docs.npmjs.com/generating-provenance-statements

Description of Changes:

• We added the necessary permissions to generate the npm provenance
• We added the --provenance flag to the npm publish command

Checklist

• I have self-reviewed the changes being requested
• I have updated the documentation (check issue ticket 📋Update documentation if the PR introduces a new feature!📋 #218)

[Ujstor]

@NachoVazquez Thanks for the PR. I need to create an NPM_TOKEN and test the release

[NachoVazquez]

Yes, @Ujstor, that's the only thing pending. It can be triggered manually, so you don't need to create a new version. We will just take what's on the GitHub release matching the entered version.

[NachoVazquez]

I'll be pending, so I can release v2 of GoNx, which will be powered by go-blueprint thanks to the npm package.

[Ujstor]

LGTM!

[Ujstor]

@NachoVazquez can you check pipeline logs?
https://github.com/Melkeydev/go-blueprint/actions/runs/16392461847/job/46320246793

I did a manual trigger and was prompted to input the version, so I entered v0.10.11.