feat: Kernel fix & test improvements/refactoring

[dbanks12]

Description

• Blocks fix: bump circuits, USE_TURBO, acirHash, bump circuits.js timeout aztec-packages#263
• Closes Add checks in kernel that contract_address and contract_tree_root are sane #172
• Closes Refactor private kernel tests with helper functions #213
• Some work related to: Ensure all/most hashing uses common functions in a3-circuits' hash.hpp #173
• Fixes bug introduced in: feat: check existence of vk in contract tree  #167
  • contract logic wasn't being called at all in native kernel...
  • also makes tests more robust to catch such bugs (tests input real contract tree root and check contract address output from circuit)

Status

• Blocked by chore: zero-initialize all structs & their members and arrays #233
• Needs to be rebased on master which will be some work.
• I want to decide if there is a better way to handle private circuit call args than the way I am in this PR.
  • Decided to punt this for now since this issue now blocks fix: bump circuits, USE_TURBO, acirHash, bump circuits.js timeout aztec-packages#263
  • Created issue for this: Find a more generic (type-agnostic) way to define private call args but still allow private call functions to be passed into test helper func #246
• Need to comment helper functions in hash.hpp.

Contents

• Kernel tests have been refactored to use helper functions.
• Hash/tree functions have been moved into helpers in hash.hpp (for kernel at least).
• Fixed native kernel circuit which was not calling any contract logic.
• Changed the way args are passed to private circuit calls so that we can use a std::function type to write functions that accept any circuit function as input.

Checklist:

• I have reviewed my diff in github, line by line.
• Every change is related to the PR description.
• I have linked this pull request to the issue(s) that it resolves.
• There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
• There are no circuit changes, OR specifications in /specs have been updated.
• There are no circuit changes, OR a cryptographer has been assigned for review.
• I've updated any terraform that needs updating (e.g. environment variables) for deployment.
• The branch has been rebased against the head of its merge target.
• I'm happy for the PR to be merged at the reviewer's next convenience.
• New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
• If existing code has been modified, such documentation has been added or updated.

Note
If you are updating the submodule, please make sure you do it in its own special PR and avoid making changes to the submodule as a part of other PRs.
To update a submodule, you can run the following commands:

$ git submodule update --recursive

Alternatively, you can select a particular commit in barretenberg/aztec3 that you wish to point to:

$ cd barretenberg
$ git pull origin aztec3        # This will point to the latest commit in `barretenberg/aztec3`
$ git checkout <commit_hash>    # Use this if you wish to point to a particular commit.
$ cd ..
$ git add . && git commit -m <commit_msg>
$ git push

[iAmMichaelConnor]

I think this TODO has been fixed, so this comment can be removed.

[dbanks12]

@iAmMichaelConnor this is the big chunk we should be able to remove once we have the special kernel version for the initial iteration. Won't need to compute the mock kernel anymore.