bug #2954 [CI] Fix npm releases with pnpm (Kocal)

This PR was merged into the 2.x branch.

Discussion
----------

[CI] Fix npm releases with pnpm

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | no <!-- please update src/**/CHANGELOG.md files -->
| Docs?         | no <!-- required for new features -->
| Issues        | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead -->
| License       | MIT

Given https://docs.npmjs.com/using-private-packages-in-a-ci-cd-workflow, https://pnpm.io/using-changesets#add-a-publish-script, or pnpm/pnpm#3141

It should works better now.

⚠️ no need to release a 2.28.2 right now, I already manually published packages on npm for 2.28.1 version

Commits
-------

4061a42 [CI] Fix npm releases with pnpm

Author: Kocal

.github/workflows/release-on-npm.yaml

@@ -40,9 +40,12 @@ jobs:
               git add .
               git commit -m "Update versions to ${{ env.VERSION }}"
 
-          - name: Publish on NPM
+          - name: Configure NPM authentication
+            run: pnpm config set '//registry.npmjs.org/:_authToken' "${NODE_AUTH_TOKEN}"
             env:
-              NPM_AUTH_TOKEN: ${{ secrets.NPM_PUBLISH_TOKEN }}
+              NODE_AUTH_TOKEN: ${{secrets.NPM_PUBLISH_TOKEN}}
+
+          - name: Publish on NPM
             run: pnpm publish --recursive --access public --no-git-checks
 
           - name: Push changes