chore!: Remove recursive from ACIR format; add them to API and CLI

[aakoshh]

Resolves noir-lang/noir#6185

• Remove the recursive field from ACIR formats and the Circuit definition
• Add --recursive to bb CLI
• Add recursive to main.ts, the backend API and Wasm

This is effectively undoing a lot of what was done here. Interestingly there many more Wasm methods that need the recursive parameter now: whereas previously only acir_create_proof and acir_verify_proof used it, now anything that calls create_circuit needs it because circuit creation builds all the constraints already, which depend on this.

TODO:

• Remove the #[recursive] attribute from Noir
• Should the "prove and verify" methods that return nothing have a recursive parameter?
• Remove #[recursive] from noir-protocol-circuits
• Update bb-prover where it uses uses noir-protocol-circuits to use the correct recursive flag
• Add --recursive to cli.ts under bb-prover
• Check all calls to executeBB and pass --recursive if it calls a bb command that needs it

[TomAFrench]

Should the "prove and verify" methods that return nothing have a recursive parameter?

I think yes as we could want to test recursive proof generation (these methods are mostly used for our CI)

[TomAFrench]

Just need to re-add recursive testing for assert_statement. We should be good to go after this.

[TomAFrench]

Looks like there's a bash issue with adding the recursive flag to the CLI args.