chore: add support for caching node_modules within a nested repository

ci3/npm_install_deps

@@ -3,13 +3,14 @@
 # Note this cache pull won't restore .yarn, which means a subsequent "yarn install" may still be slow.
 # This doesn't matter in CI however.
 NO_CD=1 source ${root:-$(git rev-parse --show-toplevel)}/ci3/source
+REPO_PATH=$(git rev-parse --show-toplevel)
 
 if [ ! -f yarn.lock ]; then
   echo_stderr "yarn.lock not found in $PWD."
   exit 1
 fi
 
-yarn_lock_path=$(realpath yarn.lock --relative-to=$root)
+yarn_lock_path=$(realpath yarn.lock --relative-to=$REPO_PATH)
 
 if [ "$CI" -eq 1 ]; then
   nm_hash=$(cache_content_hash "^$yarn_lock_path")

noir/bootstrap.sh

@@ -88,18 +88,12 @@ function build_packages {
   if cache_download noir-packages-$hash.tar.gz; then
     cd noir-repo
     npm_install_deps
-    # Hack to get around failure introduced by https://github.com/AztecProtocol/aztec-packages/pull/12371
-    # Tests fail with message "env: ‘mocha’: No such file or directory"
-    yarn install
     return
   fi
 
   cd noir-repo
   npm_install_deps
 
-  # Hack to get around failure introduced by https://github.com/AztecProtocol/aztec-packages/pull/12371
-  # Tests fail with message "env: ‘mocha’: No such file or directory"
-  yarn install
   yarn workspaces foreach  -A --parallel --topological-dev --verbose $js_include run build
 
   # We create a folder called packages, that contains each package as it would be published to npm, named correctly.