fix(ci): restore npm registry-url for OIDC trusted publish

Even with Node 22 and id-token permissions, npm publish was failing in release with ENEEDAUTH, meaning trusted publishing was not being engaged.\n\nsetup-node's registry-url configuration is part of npm's recommended trusted publishing setup. This restores registry-url in all release jobs while keeping token cleanup to avoid stale token fallback.\n\nRef: #9

Author: stevenobiajulu

.github/workflows/release.yml

@@ -32,6 +32,7 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 22
+          registry-url: https://registry.npmjs.org
           cache: npm
 
       - name: Use npm 11.5.1+ for OIDC trusted publishing compatibility
@@ -163,6 +164,7 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 22
+          registry-url: https://registry.npmjs.org
           cache: npm
 
       - name: Use npm 11.5.1+ for OIDC trusted publishing compatibility
@@ -227,6 +229,7 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 22
+          registry-url: https://registry.npmjs.org
           cache: npm
 
       - name: Use npm 11.5.1+ for OIDC trusted publishing compatibility