feat: aztec-up installs without docker

[charlielye]

Now we're shipping bb in bb.js for supported architectures/os's, we can support installs without needing docker.
The user does however need a distribution with:

• The minimum required node version.
• Tools e.g: make, gcc, python, git.

Note: You will not be able to do backend proving as we don't ship bb-avm. This is contract development only. Provers/validators are expected to still use the release image.

This PR:

• boxes and aztec-up no longer depends on release-image.
• We test aztec-up with a local npm registry (verdaccio) that we prime with the monorepo packages.
• New install script that installs correct versions of:
  • nargo
  • foundry
  • jq
  • packages @aztec/aztec, @aztec/cli-wallet, bb via @aztec/bb.js.
• ./bootstrap.sh versions outputs all expected versions of relevant tools (used by aztec-up).
• boxes now build and test without any requirement on a release image (they start the local network directly).
• Remove unwanted npx aztec-create stuff from boxes.
• Remove some never used log commands from ci.sh.
• Rework some bootstrap release stuff so we can easily get paths to packages to be released (helps load into verdaccio).
• Remove interactive query from noir precommit hook as they can't be interactive.
• Move the nasty aztec cli extension script(s) out of aztec-up and into yarn-project/aztec/scripts/aztec.sh and make it the entrypoint. The script was only every meant to abstract away the docker container but additional functionality made its way in. This functionality should probably all be TS code, but for now at least it's owned by the cli package. Extensions are test, compile, new, init.

TODO:

• Add test to release-image as it's no longer tested.
• Maybe go back to bb and bb-no-avm (invert), and ship bb in bb.js, but in architecture specific packages (with wrapper package). Separating required as the binary with avm is 174mb. The no avm version of bb is really for crypto team workflow optimisation, so we should simplify.

[charlielye]

Flakey Tests

🤖 says: This CI run detected 1 tests that failed, but were tolerated due to a .test_patterns.yml entry.

\033FLAKED\033 (\0338;;http://ci.aztec-labs.com/1fb671609e410e87�1fb671609e410e878;;�\033): yarn-project/end-to-end/scripts/run_test.sh simple src/e2e_p2p/inactivity_slash_with_consecutive_epochs.test.ts (522s) (code: 1) group:e2e-p2p-epoch-flakes (\033Charlie Lye\033: wip)

[olehmisar]

hi. Any chance we can have automatic aztec version selection by specifying the aztec version inside a dotfile per each project. Similar to gaztec: https://github.com/nemi-fi/gaztec

[charlielye]

• feat: aztec-up can be used to manage multiple aztec versions #19261
• feat: aztec-up installs without docker #18665 👈 (View in Graphite)
• next

This stack of pull requests is managed by Graphite. Learn more about stacking.