fix(cli): Only lock the packages selected in the workspace

[aakoshh]

Description

Problem*

Related to #7335

Summary*

Changes the nargo CLI to take out individual locks on the packages affected by the commands, rather than the workspace level Nargo.toml file, so that we can execute commands in parallel.

Also fixes the issue where the target changed depending on whether we use --package to select a member in the workspace or whether we cd into the directory of the member itself. We always want it to be the workspace level target.

Additional Context

#6752 changed the CLI to look for the first package on the ancestor path when neither --workspace nor --package options were present, and treat that as the Workspace, which resulted in the target directory being different in the two cases. Now we always look for the top level Nargo.toml, ie. the workspace, so that we use the correct target. We look for both the top and bottom level workspaces; if they differ, then we consider the bottom one as the selected member.

#6941 moved the locks from the integration tests into nargo itself, where it was easier to manage, however it interfered with the CI scripts using parallel to run CLI commands concurrently because the lock was taken out on the entire workspace.

Testing

Here's a session demonstrating that indeed on master if we execute a member the artefacts are saved in its own target directory, whereas on this branch they go into the workspace level one (note how different packages write to different output files in the common directory, so they don't conflict):

$ cd test_programs/execution_success/workspace
$ ls
Nargo.toml  crates/     target/
$ ls crates
a/ b/
$ rm -rf target
$ cd crates/a 
$ ls
Nargo.toml   Prover.toml  src/
$ git checkout master
Switched to branch 'master'
Your branch is up to date with 'origin/master'.
$ cargo run -q -p nargo_cli -- --program-dir . execute 
[a] Circuit witness successfully solved
[a] Witness saved to /Users/aakoshh/Work/aztec/noir/test_programs/execution_success/workspace/crates/a/target/a.gz
$ ls target
a.gz    a.json
$ rm -rf target
$ git checkout fix-cli-locking
Switched to branch 'fix-cli-locking'
Your branch is up to date with 'origin/fix-cli-locking'.
$ cargo run -q -p nargo_cli -- --program-dir . execute
[a] Circuit witness successfully solved
[a] Witness saved to /Users/aakoshh/Work/aztec/noir/test_programs/execution_success/workspace/target/a.gz
$ ls
Nargo.toml   Prover.toml  src/
$ ls ../../target
a.gz    a.json
$ cargo run -q -p nargo_cli -- execute
[a] Circuit witness successfully solved
[a] Witness saved to /Users/aakoshh/Work/aztec/noir/test_programs/execution_success/workspace/target/a.gz
$ cargo run -q -p nargo_cli -- execute --workspace
[a] Circuit witness successfully solved
[a] Witness saved to /Users/aakoshh/Work/aztec/noir/test_programs/execution_success/workspace/target/a.gz
[b] Circuit witness successfully solved
[b] Witness saved to /Users/aakoshh/Work/aztec/noir/test_programs/execution_success/workspace/target/b.gz
$ cargo run -q -p nargo_cli -- execute --package b
[b] Circuit witness successfully solved
[b] Witness saved to /Users/aakoshh/Work/aztec/noir/test_programs/execution_success/workspace/target/b.gz

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.

[asterite]

Great refactor, looks good!