Fix: Remove registry-url from setup-node to resolve NODE_AUTH_TOKEN conflicts

- Removed registry-url parameter from setup-node action in ci.yml and release.yml
- Registry configuration now handled exclusively by .npmrc file
- Auth tokens configured via npm config commands with ECHO_LIBRARIES_ACCESS_KEY
- Eliminates NODE_AUTH_TOKEN environment variable creation and logging
- Fixes 403 Forbidden errors during npm ci with Echo registry
- Maintains dual-registry support: Echo for dependencies, GitHub for publishing

Changes:
- .github/workflows/ci.yml: Removed registry-url from setup-node
- .github/workflows/release.yml: Removed registry-url from setup-node

This ensures proper authentication with Echo (npm.echohq.com) registry while avoiding conflicts with GitHub Actions' automatic NODE_AUTH_TOKEN creation.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

Author: cx-atish-jadhav

.github/workflows/ci.yml

@@ -34,7 +34,6 @@ jobs:
         uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: 22.11.0
-          registry-url: https://npm.echohq.com/
       - name: Configure echohq auth (both hosts)
         env:
           ECHO_LIBRARIES_ACCESS_KEY: ${{ secrets.ECHO_LIBRARIES_ACCESS_KEY }}

.github/workflows/release.yml

@@ -99,7 +99,6 @@ jobs:
       - uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
         with:
           node-version: 22.11.0
-          registry-url: https://npm.echohq.com/
 
       # CONFIGURE ECHOHQ AUTH
       - name: Configure echohq auth (both hosts)