chore: Update package release workflow

We were using `github.event.release.tag_name` to set the new version of the package, but the tag_name in question contains a leading 'v' (`v4.0.0` for example) which breaks the workflow (invalid semver version, it expects `4.0.0` instead).

Since we are currently bumping the version manually anyway, we can just call yarn publish with the `--non-interactive` flag, which will set the version to the current version defined in package.json (see yarnpkg/yarn#5748).
That's exactly what we want in this context.

.github/workflows/deploy-release-to-npm.yml

@@ -22,8 +22,11 @@ jobs:
       - name: Install dependencies
         run: yarn install --frozen-lockfile
 
+      # Make sure you have bumped the version before publishing the release
+      # This script will not bump the version and will use the version from package.json
+      # It will just fail if trying to publish an already published version
       - name: Build and publish the package
-        run: yarn publish --new-version ${{ github.event.release.tag_name }}
+        run: yarn publish --non-interactive
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
@@ -36,4 +39,4 @@ jobs:
         run: |
           git add package.json
           git commit -m "chore: Release ${{ github.event.release.tag_name }}"
-          git push origin master
+          git push origin master