fix: better update steps for dockerized sandbox

[alexghr]

Improves error message shown to user when running the update command in the CLI if dockerized Sandbox is out of date.

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).

[AztecBot]

Benchmark results

No metrics with a significant change found.

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 ed144b19 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	223,032	868,148	3,449,504
l1_rollup_execution_gas	842,119	3,595,256	22,204,873
l2_block_processing_time_in_ms	2,004 (+1%)	7,564 (+1%)	29,894 (+1%)
note_successful_decrypting_time_in_ms	298 (+2%)	869 (+1%)	3,183 (+2%)
note_trial_decrypting_time_in_ms	100 (+4%)	77.0 (+15%)	133 (-1%)
l2_block_building_time_in_ms	13,304 (+2%)	52,894 (+1%)	211,333 (+1%)
l2_block_rollup_simulation_time_in_ms	11,970 (+2%)	47,576 (+1%)	190,048 (+1%)
l2_block_public_tx_process_time_in_ms	1,293 (+1%)	5,178 (+1%)	20,790 (+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	21,461 (-1%)	42,005 (-2%)
note_history_successful_decrypting_time_in_ms	1,995 (-3%)	3,888 (-3%)
note_history_trial_decrypting_time_in_ms	136 (+12%)	144 (+1%)
node_database_size_in_bytes	1,633,425	1,099,372
pxe_database_size_in_bytes	29,748	59,307

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	778 (-1%)	61,697	18,905
private-kernel-ordering	123 (-1%)	24,297	8,153
base-rollup	1,771	656,311	814
root-rollup	81.6 (+8%)	4,072	1,097
private-kernel-inner	785 (-1%)	81,568	18,905
public-kernel-private-input	41.6	41,519	18,841
public-kernel-non-first-iteration	26.4	41,497	18,841
merge-rollup	0.957	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,787	27,548

[rahul-kothari]

Ah damn only just saw - think this is a bad idea ->

1. The link will probably change [why does it say "cli/updating"]
2. Error message doesn't say what section to follow. A new/confused dev wouldn't know if they have to do everything or nothing. Maybe literally just show the curl command?