feat!: Unify ABIs between nargo and yarn-project (AztecProtocol#3989)

Changes the output of `nargo` and `noir-wasm` to generate a single
artifact that includes debug information. Compiled contracts now have a
`file_map` at the root of the artifact, and a `debug_symbols` within
each function. For consistency, compiled programs also have `file_map`
and `debug_symbols`. Debug symbols are compressed and base64-encoded, as
they were by the former `noir-compiler` postprocessing. The `debug` json
artifact is no longer emitted.

Removes all code related to generating `yarn-project`-specific ABIs from
noir compiler. Instead, `types` now exposes a `loadContractArtifact`
that renames fields as needed (and use camel instead of snake case), and
is required when loading a noir contract artifact. Autogenerated types
run this automatically.

Since we are no longer post-processing artifacts, the `noir-contracts`
project shape is changed. JSON files live in the `target` folder where
nargo outputs them (this is not configurable), and are loaded by the
autogenerated typescript interfaces from there.

As part of the refactor, moves functions for getting functions debug
info out of `acir-simulator` and into `types`.

**Breaking change**: This removes the need to run `codegen` for using a
compiled contract. However, when creating a new contract object from
aztec.js, a dev needs to call `loadContractArtifact`.

**Future changes**: Type information for a compilation artifact is now
spread all over the place, and duplicated in more than one place. There
are types defined within rust code in Noir as
`[wasm_bindgen(typescript_custom_section)]`, others defined within
typescript code in the `noir_wasm` package, others in `foundation`, and
others in `types`. We should unify it in a single place.

Fixes AztecProtocol#3812

Supersedes AztecProtocol#3906

Noir subrepo has been pushed to
noir-lang/noir#4035 to run the Noir CI

Author: spalladino

boxes/blank-react/tsconfig.json

@@ -21,5 +21,5 @@
     "skipLibCheck": true,
     "jsx": "react-jsx"
   },
-  "include": ["src", "src/artifacts/Blank.json"]
+  "include": ["src", "src/contracts/target/*.json"]
 }

boxes/blank/tsconfig.json

@@ -21,5 +21,5 @@
     "skipLibCheck": true,
     "jsx": "react-jsx"
   },
-  "include": ["src", "src/artifacts/Blank.json"]
+  "include": ["src", "src/contracts/target/*.json"]
 }

boxes/token/tsconfig.json

@@ -21,5 +21,5 @@
     "skipLibCheck": true,
     "jsx": "react-jsx"
   },
-  "include": ["src", "src/artifacts/Token.json"]
+  "include": ["src", "src/contracts/target/*.json"]
 }

docs/docs/dev_docs/contracts/compiling.md

@@ -18,23 +18,11 @@ aztec-nargo compile
 
 This will output a JSON [artifact](./artifacts.md) for each contract in the project to a `target` folder containing the Noir ABI artifacts.
 
-Before you can use the ABI it currently needs to be validated as being Aztec compatible, and transformed to an Aztec compatible ABI using `aztec-cli codegen`, passing a Noir ABI file or folder, and output location, e.g:
-
-```bash
-aztec-cli codegen ./aztec-nargo/output/target/path -o src/artifacts
-```
-
-It can be useful to perform this compilation, validation and transformation in one go, so you may wish to chain the commands and perhaps add them to a package.json script. The below assumes your contract is in a folder called `contract` at your project root:
-
-```bash
-(cd contract && aztec-nargo compile && aztec-cli codegen target -o ../src/artifacts)
-```
-
 ### Typescript Interfaces
 
-You can use the codegenerator to autogenerate type-safe typescript classes for each of your contracts. These classes define type-safe methods for deploying and interacting with your contract based on their artifact.
+You can use the code generator to autogenerate type-safe typescript classes for each of your contracts. These classes define type-safe methods for deploying and interacting with your contract based on their artifact.
 
-To generate them, include a `--ts` option in the codegen command with a path to the target folder for the typescript files:
+To generate them, include a `--ts` option in the `codegen` command with a path to the target folder for the typescript files:
 
 ```bash
 aztec-cli codegen ./aztec-nargo/output/target/path -o src/artifacts --ts

docs/docs/dev_docs/contracts/deploying.md

@@ -33,7 +33,7 @@ Compile the contract:
 aztec-nargo compile
 ```
 
-Generate the ABI and typescript class:
+Generate the typescript class:
 
 ```bash
 aztec-cli codegen ./aztec-nargo/output/target/path -o src/artifacts --ts

docs/docs/dev_docs/getting_started/aztecnr-getting-started.md

@@ -156,7 +156,7 @@ aztec-nargo compile
 
 This will compile the smart contract and create a `target` folder with a `.json` artifact inside.
 
-After compiling, you need to generate the ABI and typescript class. In the same directory, run this:
+After compiling, you can generate a typescript class. In the same directory, run this:
 
 ```bash
 aztec-cli codegen target -o src/artifacts --ts

docs/docs/dev_docs/tutorials/uniswap/typescript_glue_code.md

@@ -33,7 +33,7 @@ and the each of the Aztec.nr contracts by going into each folder and running:
 aztec-nargo compile
 ```
 
-And then generate the ABIs and typescript interface:
+And then generate the typescript interface:
 
 ```bash
 aztec-cli codegen ./target/ -o ../../../src/test/fixtures uniswap --ts

docs/docs/dev_docs/tutorials/writing_dapp/contract_deployment.md

@@ -42,14 +42,6 @@ Now run the following from your contract folder (containing Nargo.toml):
 aztec-nargo compile
 ```
 
-Once you have compiled your contracts, you need to generate the ABIs:
-
-```sh
-aztec-cli codegen ./target/path -o src/artifacts --ts
-```
-
-This should have created an artifact `contracts/token/src/artifacts/Token.json` with the interface and bytecode for your contract.
-
 ## Deploy your contracts
 
 Let's now write a script for deploying your contracts to the Sandbox. We'll create a Private eXecution Environment (PXE) client, and then use the `ContractDeployer` class to deploy our contracts, and store the deployment address to a local JSON file.
@@ -61,7 +53,8 @@ Create a new file `src/deploy.mjs`:
 import { writeFileSync } from 'fs';
 import { Contract, ContractDeployer, createPXEClient } from '@aztec/aztec.js';
 import { getInitialTestAccountsWallets } from '@aztec/accounts/testing';
-import TokenContractArtifact from "../contracts/token/target/Token.json" assert { type: "json" };
+import TokenContractJson from "../contracts/token/target/token_contract-Token.json" assert { type: "json" };
+
 
 #include_code dapp-deploy yarn-project/end-to-end/src/sample-dapp/deploy.mjs raw
 

docs/docs/dev_docs/tutorials/writing_dapp/contract_interaction.md

@@ -18,7 +18,7 @@ To do this, let's first initialize a new `Contract` instance using `aztec.js` th
 // src/contracts.mjs
 import { Contract } from "@aztec/aztec.js";
 import { readFileSync } from "fs";
-import TokenContractArtifact from "../contracts/token/src/artifacts/Token.json" assert { type: "json" };
+import TokenContractJson from "../contracts/token/target/token_contract-Token.json" assert { type: "json" };
 ```
 
 And then add the following code for initializing the `Contract` instances:

docs/docs/dev_docs/tutorials/writing_private_voting_contract.md

@@ -193,18 +193,16 @@ The easiest way to compile the contract is with `aztec-nargo`. Run the following
 aztec-nargo compile
 ```
 
-This will create a new directory called `target` and a JSON artifact inside it. To create the Aztec contract ABI and typescript interface, run:
+This will create a new directory called `target` and a JSON artifact inside it. To optionally create a typescript interface, run:
 
 ```bash
 aztec-cli codegen target -o src/artifacts --ts
 ```
 
-This will create the ABI called `Voting.json` in `src/artifacts`. If you are getting some errors here you might want to check out the [debugging page](../debugging/main.md).
-
 Once it is compiled you can [deploy](../contracts/deploying.md) it to the sandbox. Ensure your [sandbox is running](../cli/sandbox-reference.md) and run this in the same dir as before:
 
 ```bash
-aztec-cli deploy ./src/artifacts/Voting.json --args $ADMIN_ADDRESS
+aztec-cli deploy ./target/Voting.json --args $ADMIN_ADDRESS
 ```
 
 The constructor takes an address as an argument to set the admin, so you can use an address that is deployed with the sandbox - check the sandbox terminal or run `aztec-cli get-accounts`.
@@ -214,7 +212,7 @@ You should see a success message with the contract address. Now we can start cal
 Cast a vote like this:
 
 ```bash
-aztec-cli send cast_vote --contract-artifact ./src/artifacts/Voting.json --contract-address $CONTRACT_ADDRESS --args 1 --private-key $PRIVATE_KEY
+aztec-cli send cast_vote --contract-artifact ./target/Voting.json --contract-address $CONTRACT_ADDRESS --args 1 --private-key $PRIVATE_KEY
 ```
 
 You can get the contract address from the sandbox terminal or the message printed when you deployed the contract. You can also get a private key from the sandbox terminal, or generate one with `aztec-cli generate-private-key`.
@@ -226,7 +224,7 @@ You can now try running this command again to ensure our nullifier works.
 Get the number of votes like this:
 
 ```bash
-aztec-cli call get_vote --contract-artifact ./src/artifacts/Voting.json --contract-address $CONTRACT_ADDRESS --args 1
+aztec-cli call get_vote --contract-artifact ./target/Voting.json --contract-address $CONTRACT_ADDRESS --args 1
 ```
 
 This should return `1n`.