feat: dockerize aztec-cli

[alexghr]

This PR dockerizes aztec-cli. It requires #2737 to be merged in first.

Fix #2875

Checklist:

Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

• If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
• I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
• Every change is related to the PR description.
• I have linked this pull request to relevant issues (if any exist).

[spypsy]

LGTM!
Don't understand tho how will this be installed when users add the sandbox docker-compose? Do we need to update the sandbox.aztec.network script to also download the aztec-cli script?

[alexghr]

Hey, yep there's a PR updating the sandbox installation script that copies this script to ~/.aztec/bin

[alexghr]

A note on this:
I tried using the sandbox image instead of building a new docker image but two reasons why I didn't do that:
(1) the sandbox image runs yarn focus to trim down the number of dependencies so the cli's deps aren't available
(2) in the bash wrapper I'd have to point the entrypoint to a internal path inside the container (/usr/src/yarn-project/cli/dest/bin/index.js). If in the future the container's internal layout changes then the bash wrapper would stop working

[AztecBot]

Benchmark results

Metrics with a significant change:

• circuit_simulation_time_in_ms (base-rollup): 2,084 (+18%)
• node_history_sync_time_in_ms (5): 25,105 (+17%)
• node_history_sync_time_in_ms (10): 49,143 (+16%)
• l2_block_processing_time_in_ms (32): 8,723 (+17%)
• l2_block_processing_time_in_ms (128): 34,363 (+16%)
• note_trial_decrypting_time_in_ms (32): 119 (+75%)

Detailed results

All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.

This benchmark source data is available in JSON format on S3 here.

Values are compared against data from master at commit 6c20b459 and shown if the difference exceeds 1%.

L2 block published to L1

Each column represents the number of txs on an L2 block published to L1.

Metric	8 txs	32 txs	128 txs
l1_rollup_calldata_size_in_bytes	45,444	179,588	716,132
l1_rollup_calldata_gas	222,924	868,244	3,449,084
l1_rollup_execution_gas	842,011	3,595,352	22,204,453
l2_block_processing_time_in_ms	2,309 (+14%)	⚠️ 8,723 (+17%)	⚠️ 34,363 (+16%)
note_successful_decrypting_time_in_ms	278 (-7%)	798 (-7%)	2,917 (-7%)
note_trial_decrypting_time_in_ms	78.0 (-24%)	⚠️ 119 (+75%)	137 (+2%)
l2_block_building_time_in_ms	14,552 (+11%)	57,737 (+11%)	230,357 (+11%)
l2_block_rollup_simulation_time_in_ms	13,243 (+12%)	52,514 (+12%)	209,284 (+12%)
l2_block_public_tx_process_time_in_ms	1,274	5,097	20,403 (-1%)

L2 chain processing

Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric	5 blocks	10 blocks
node_history_sync_time_in_ms	⚠️ 25,105 (+17%)	⚠️ 49,143 (+16%)
note_history_successful_decrypting_time_in_ms	1,934 (-3%)	3,784 (-3%)
note_history_trial_decrypting_time_in_ms	121 (-1%)	147 (+2%)
node_database_size_in_bytes	1,633,698	1,101,206
pxe_database_size_in_bytes	27,188	54,187

Circuits stats

Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit	circuit_simulation_time_in_ms	circuit_input_size_in_bytes	circuit_output_size_in_bytes
private-kernel-init	82.2 (+14%)	61,697	18,841
private-kernel-ordering	50.8 (+17%)	24,233	8,089
base-rollup	⚠️ 2,084 (+18%)	656,309	811
root-rollup	89.9 (+16%)	4,072	1,097
private-kernel-inner	59.1 (+12%)	81,504	18,841
public-kernel-private-input	46.4 (+12%)	41,455	18,841
public-kernel-non-first-iteration	28.7 (+9%)	41,497	18,841
merge-rollup	0.790 (-11%)	2,592	873

Miscellaneous

Transaction sizes based on how many contracts are deployed in the tx.

Metric	0 deployed contracts	1 deployed contracts
tx_size_in_bytes	8,723	27,240