fix(ci): fix npmjs.org publish using wrong registry (was publishing to GitHub Packages)

- Add scope parameter to Setup Node (npmjs.org) step to ensure correct registry
- Add E409 error detection for GitHub Packages "Cannot publish over existing version"
- Fixes issue where npmjs publish was incorrectly targeting npm.pkg.github.com

Author: mars167

.git-ai/lancedb.tar.gz

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b30e7f67c4cfed10caec590edb722d7394c9dd1fb6d9631f3c4524242fb84bea
-size 314594
+oid sha256:0f3f8d0af5e9f05f0d5d1ba1c83a7dcbaddaa70bb80159dc93de0a520732fbb2
+size 314715

.github/workflows/release.yml

@@ -117,6 +117,9 @@ jobs:
           if grep -q "You cannot publish over the previously published versions" publish_output.txt; then
             echo "::notice::Version already exists on GitHub Packages, skipping"
             echo "skipped=true" >> "$GITHUB_OUTPUT"
+          elif grep -q "Cannot publish over existing version" publish_output.txt; then
+            echo "::notice::Version already exists on GitHub Packages (E409), skipping"
+            echo "skipped=true" >> "$GITHUB_OUTPUT"
           elif grep -q "^\+ @${{ github.repository_owner }}/git-ai@" publish_output.txt; then
             echo "::notice::Successfully published to GitHub Packages"
             echo "skipped=false" >> "$GITHUB_OUTPUT"
@@ -142,6 +145,7 @@ jobs:
         with:
           node-version: "22"
           registry-url: "https://registry.npmjs.org"
+          scope: "@mars167"
 
       - name: Publish to npmjs.org
         if: ${{ env.RELEASE_TAG != '' }}