fix: ensure new release artifacts get published

The default GITHUB_TOKEN doesn't trigger further pipelines. As a
consequence, the automatically created release did not trigger the
publish pipeline on the newly created tag. This commit migrates to a
personal access token to avoid this as described in:
https://docs.github.com/en/actions/using-workflows/triggering-a-workflow

Author: languitar

.github/workflows/release.yml

@@ -43,7 +43,7 @@ jobs:
         run: npm ci
       - name: Dry-run release
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.RELEASE_TOKEN }}
         # We need to convince semantic-release to not pick up some
         # configuration from the CI environment by removing the variable that
         # is used for CI detection.
@@ -71,5 +71,5 @@ jobs:
         run: npm ci
       - name: Release
         env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.RELEASE_TOKEN }}
         run: npx semantic-release