fix: avoid npm uplink for aztec-up local publishes

[alexghr]

Summary:

• Keep @aztec/* local in the aztec-up Verdaccio build registry so publishing Aztec packages does not depend on npmjs uplink health.
• Continue proxying other scoped and unscoped packages to npmjs for dependency cache priming.

CI failure investigated:

• PR feat: merge-train/spartan #23344 failed ./bootstrap.sh, ci/x-full-no-test-cache, and npm publish contexts.
• Downloaded logs with yarn ci dlog: f5535395aab63996, 1779189592567743, and 51444ba79e6c8a4a.
• The direct npm publish log failed with E503: one of the uplinks is down, refuse to publish, while publishing @aztec/protocol-contracts to local Verdaccio.

Validation:

• bash -n aztec-up/bootstrap.sh

[spalladino]

/claudebox package @aztec/viem is not published locally, we need to allow it to be proxied. Add it as an exception to the @aztec/* wildcard at the top. Also scan for other packages as well that are not published locally. Also bring in the publish: allow_offline setting from branch cb/dd69e1f0bb2f if it makes sense.

[AztecBot]

⏳ Run #1 — Session completed (10m)
Live status

Added @aztec/viem as an npm exception in docs/examples/ts/lib.sh (only @aztec/* package not local — others use link: prefix already) and brought in publish: allow_offline: true from cb/dd69e1f0bb2f. Full analysis: https://gist.github.com/AztecBot/fcbb5ff446d16891e758bcba38632ef3

• Created PR #23397: fix: route @aztec/viem to npm in docs examples + verdaccio allow_offline
• Gist: Analysis: npm proxy exception for @aztec/viem and allow_offline verdaccio setting