fix(ci): add registry-url for npm OIDC trusted publishing (#756)

## Summary

- Fixes `ENEEDAUTH` in npm publish:
https://github.com/amd/gaia/actions/runs/24280576961
- **Root cause:** `setup-node` without `registry-url` never creates the
`.npmrc` that maps `NODE_AUTH_TOKEN` to the npm registry. npm's OIDC
trusted publishing needs this to authenticate.
- **Note:** The old `publish-npm-ui.yml` was never actually run (zero
successful runs in history) — v0.17.0 and v0.17.1 were published outside
CI. So the old workflow's lack of `registry-url` was an untested bug
too.
- **Fix:** Add `registry-url: 'https://registry.npmjs.org'` to
`setup-node`.

## Test plan

- [ ] Merge, move tag, verify npm publish authenticates and succeeds

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: kovtcharov

.github/workflows/publish.yml

@@ -361,7 +361,10 @@ jobs:
       - uses: actions/checkout@v6
       - uses: actions/setup-node@v6
         with:
-          node-version: '22'
+          # Node 24 ships with npm 11+ which supports OIDC trusted publishing.
+          # Node 22 ships with npm 10.x which does NOT — and `npm install -g
+          # npm@latest` on Node 22 runners corrupts npm's own dependencies.
+          node-version: '24'
       - name: Download validated build
         uses: actions/download-artifact@v6
         with: