feat(cli): add noir-execute binary

[aakoshh]

Description

Problem*

Resolves #7383

Summary*

Created a new tooling/artifact_cli crate which is both a library and a binary:

• exports fs utilities to read inputs and write witnesses; this is currently used by the acvm_cli to remove some duplication, but could be used by nargo, the profiler and the inspector (done in chore(cli): Use noir_artifact_cli::fs to read artifacts #7391)
• has a noir-execute binary which reads in a contract or a binary artefact and executes the circuit, similar to nargo execute; this could be invoked from nargo to remove some duplication (done in chore(cli): Forward nargo execute to noir_artifact_cli #7406)

Left for follow-up PRs:

• read an oracle transcript and use it to handle foreign calls (done in feat(cli): Log and replay oracle transcript #7417)
• CI integration test with artefacts and transcripts (done in feat(cli): Log and replay oracle transcript #7417)

Additional Context

Testing

$ cd test_programs/execution_success/workspace
$ cargo run -q -p nargo_cli -- compile --package a
$ ls target
a.json
$ cargo run -q -p noir_artifact_cli -- --artifact-path ./target/a.json --prover-file ./crates/a/Prover.toml --output-dir ./out
[a] Circuit witness successfully solved
[a] Witness saved to /Users/aakoshh/Work/aztec/noir/test_programs/execution_success/workspace/out/a.gz

Options

❯ cargo run -q -p noir_artifact_cli -- --help
Commands working on noir build artifacts

Usage: noir-execute [OPTIONS] --artifact-path <ARTIFACT_PATH> --prover-file <PROVER_FILE>

Options:
  -a, --artifact-path <ARTIFACT_PATH>
          Path to the JSON build artifact (either a program or a contract)

  -p, --prover-file <PROVER_FILE>
          Path to the Prover.toml file which contains the inputs and the optional return value in ABI format

  -o, --output-dir <OUTPUT_DIR>
          Path to the directory where the output witness should be saved. If empty then the results are discarded

  -w, --witness-name <WITNESS_NAME>
          Write the execution witness to named file
          
          Defaults to the name of the circuit being executed.

      --contract-fn <CONTRACT_FN>
          Name of the function to execute, if the artifact is a contract

      --oracle-resolver <ORACLE_RESOLVER>
          JSON RPC url to solve oracle calls

      --pedantic-solving
          Use pedantic ACVM solving, i.e. double-check some black-box function assumptions when solving

  -h, --help
          Print help (see a summary with '-h')

  -V, --version
          Print version

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [For Experimental Features] Documentation to be submitted in a separate PR.

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Test Suite Duration'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 2672478	Previous: d0d04e8	Ratio
AztecProtocol_aztec-packages_noir-projects_noir-protocol-circuits_crates_blob	66 s	51 s	1.29

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

[TomAFrench]

Some initial thoughts

[TomAFrench]

Can you also add some tests for this showing the usage of the CLI?

[aakoshh]

Can you also add some tests for this showing the usage of the CLI?

I created a separate story for that: #7382

[github-actions]

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark 'Compilation Time'.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.20.

Benchmark suite	Current: 2672478	Previous: d0d04e8	Ratio
regression_4709	0.889 s	0.725 s	1.23

This comment was automatically generated by workflow using github-action-benchmark.

CC: @TomAFrench

[aakoshh]

Added a test showing the usage of the transcript in #7417