feat!: Remove TOOLCHAIN logic and replace with CMake presets

[phated]

Description

Before these changes, Barretenberg was forcing specific C and C++ Compilers through the -DTOOLCHAIN variable. This is a flawed design because it doesn't allow consumers to set the CC or CXX environment variables to pick their compilers. Being able to set those values is extremely important for cross-compiling.

This PR removes all of that TOOLCHAIN logic and instead leverages CMake Presets to provide the defaults we expect (such as clang, clang-15, gcc, gcc-10 and clang from Homebrew). Shoutout to @adr1anh for sharing the idea for presets which massively helped with this transition plan.

It also updates the bootstrap.sh file to detect and print which preset should be used. If you use cmake commands directly, you'll need to start using the related preset commands.

I've also updated the dockerfiles and docs to all reference these preset commands.

The cmake/toolchains directory still exists, but the files have been re-done as proper CMake Cross-Compile Toolchain files which are really just supposed to set the target name and architecture, but can include extras like the i386 file.

I've tested this quite extensively on my Arm Mac but I need feedback for Linux, the dockerfiles, and the compare_honk_bench stuff (because it was non-standard).

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 /markdown/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.

[dbanks12]

Looks good to me. Just looking for clarification on a couple of things mentioned in my comments.

[charlielye]

Skimmed. But looks like a great step in the right direction 👍

[adr1anh]

LGTM

[adr1anh]

To address @codygunton's issue with GCC12, it seems like we can instead set the generator to Ninja in the CMakePresets.json rather than the VSCode workspace settings.

    {
      "name": "default",
      "displayName": "Build with Clang",
      "description": "Build with globally installed Clang",
      "binaryDir": "build",
      "generator": "Ninja",
      "environment": {
        "CC": "clang",
        "CXX": "clang++"
      }
    },

When testing on the mainframe, my build were being parallelized after performing this change.

On another note, switching configure preset requires the CMake cache to be rebuilt. The option is "CMake: Delete cache and reconfigure" in VSCode. This could be solved by having a separate build folder for each configuration, though that might be more annoying to setup. (i.e. build-gcc build-gcc, with build being the folder for the default configuration with clang.)

[adr1anh]

I've added a commit which sets the generator in the default preset to Ninja. The second commit tells CMake to generate a compile_commands.json file that helps the clangd language server understand how the file being edited is compiled. It required an extra argument in the config to suppress a warning from a GCC-specific compile flag.

EDIT: I had to modify the docker files to download ninja as well.

[codygunton]

VS Code integration is still kind of funky, e.g. building with wasm preset using CMake Tools is extremely slow, but it works for most common workflow, so I'm going to merge.