fix(aztec-up): allow offline publish to local verdaccio

[AztecBot]

aztec-up/bootstrap.sh spins up a local Verdaccio with proxy: npmjs on @*/* and **, then runs deploy_npm for each @aztec/*, @noir-lang/*, and @aztec/bb.js package. On publish, Verdaccio consults the npmjs uplink for existence/version checks; if the npmjs uplink is briefly unreachable, it returns 503 Service Unavailable - one of the uplinks is down, refuse to publish and the whole aztec-up-test-image build fails (e.g. #23327).

This is a "fake publish" path — we never actually consult npmjs for our own scoped packages, we just need verdaccio to accept the PUT. Verdaccio's publish.allow_offline opts into exactly that: publishes succeed when uplinks are unreachable.

Why this over enumerating namespaces in packages: without a proxy:

• We publish @aztec/* (44 packages: @aztec/bb.js + 43 yarn-project workspaces) and @noir-lang/* (5: types, noir_js, noir_codegen, noirc_abi, acvm_js). A wildcard-per-namespace works today but silently breaks the day a new scope is added.
• allow_offline: true is one line, namespace-agnostic, and only changes behaviour during the transient-failure case — the happy path still uses the uplink for normal validation and the ** proxy still primes transitive deps.

prep_test_mac already runs verdaccio with no uplinks at all (true offline) and is unaffected.

---

Created by claudebox · group: slackbot