chore(embedded-sdk): add verbose npm logging to diagnose OIDC publish

OIDC is confirmed available to the job, the token and registry-url are
cleared, yet npm still fails with ENEEDAUTH and shows no OIDC activity at
the default log level. Enable verbose npm logging on the publish step to
capture whether npm attempts the OIDC trusted-publishing exchange and any
registry rejection (npm redacts auth tokens in its logs). Temporary;
to be removed once publishing works.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

.github/workflows/embedded-sdk-release.yml

@@ -46,3 +46,8 @@ jobs:
           fi
       - run: npm ci
       - run: npm run ci:release
+        env:
+          # Temporary diagnostic: surface npm's OIDC trusted-publishing attempt
+          # and any registry rejection (npm redacts auth tokens in its logs).
+          # Remove once publishing is confirmed working.
+          NPM_CONFIG_LOGLEVEL: verbose