Fix workflow for publishing to NPM

[RichDom2185]

• Change the workflow trigger from PR merge to master push
• Do not fail the workflow when GH Actions is not supposed to publish a new version; instead, just skip the publishing step after verification.

[coveralls]

Pull Request Test Coverage Report for Build 5711452271

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 82.889%

---

Totals
Change from base Build 5711447058:	0.0%
Covered Lines:	10736
Relevant Lines:	12526

---

💛 - Coveralls

[shenyih0ng]

found this workflow that we can use: https://github.com/JS-DevTools/npm-publish, it seems to do what we want

Example workflow (publish package + tag commit):

name: Publish to npm

on:
  push:
    branches: main

jobs:
  publish:
    runs-on: ubuntu-latest
    environment: publish-npm # Await approval from maintainers
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: "16"

      - name: Publish to NPM
        uses: JS-DevTools/npm-publish@v2
        with:
          token: ${{ secrets.NPM_TOKEN }}
          dry-run: true # = npm publish --dry-run

      - name: Tag Release  # tag commit with new version (corresponds to npm version) 
        run: |
          git tag ${{ steps.publish.outputs.version }}
          git push origin ${{github.run_id}}

[martin-henz]

OK, let's try this.