fix(ci): add NODE_AUTH_TOKEN to publish step

[pedro-martins-brisa]

Description

This change is necessary because the release workflow was failing due to missing authentication when communicating with the npm registry. While the provenance statement (Sigstore) was successfully generated, the npm publish command lacked the required NODE_AUTH_TOKEN to authorize the upload to the @Brisanet scope.

Proposed Changes

• Modified .github/workflows/release.yml.
• Added the NODE_AUTH_TOKEN environment variable to the Publish step.
• Linked the environment variable to the ${{ secrets.NPM_TOKEN }} secret.

Compliance

• I have verified that this change complies with our code and contribution policies.
• I have verified that this change does not cause regressions and does not affect other parts of the code.

References

• npm-publish documentation
• GitHub Actions: setup-node official guide

Concluding

This fix addresses the npm error 404 Not Found and the Access token expired or revoked notice observed in the previous failed run (Attempt 1 of run 21247953800).