fix: ci-barretenberg-full mode fixes

[johnathan79717]

Summary

Multiple fixes for ci-barretenberg-full mode:

1. Create libbb-external.a - Single static library for barretenberg-rs that bundles barretenberg + env + vm2_stub
2. Propagate AVM env var - Pass AVM environment variable to isolated docker containers so tests use the correct bb binary
3. Denoise barretenberg-rs - Add denoise to build and test commands for cleaner CI output

Problem

ci-barretenberg-full mode was failing with multiple issues:

1. barretenberg-rs build failed with:

   error: could not find native static library `vm2`, perhaps an -L flag is missing?
   

   This happened because ci-barretenberg-full builds with AVM=0, so libvm2.a is not produced.

2. acir_tests failed with:

   barretenberg/cpp/build/bin/bb-avm: No such file or directory
   

   The AVM environment variable wasn't being passed to isolated docker containers, causing find-bb to incorrectly select bb-avm instead of bb.

Solution

1. Create libbb-external.a that includes everything barretenberg-rs needs:

   • All objects from libbarretenberg.a
   • env module (logstr, throw_or_abort_impl, env_hardware_concurrency)
   • vm2_stub (provides stub for create_avm2_recursion_constraints_goblin)

   This simplifies linking in barretenberg-rs to just one library and removes the need for --allow-multiple-definition and --start-group/--end-group.

2. Propagate AVM env var to isolated docker containers in ci3/docker_isolate

3. Use denoise for barretenberg-rs build and test commands

Caching

libbb-external.a is built to build/lib/ and the native build cache uploads build/{bin,lib}, so it will be cached automatically.

[ludamad]

See above

[johnathan79717]

Will ask for review again once ci-barretenberg-full passes.

[johnathan79717]

Re: why linking barretenberg.a isn't enough:

From barretenberg/cpp/src/CMakeLists.txt:

# For this library we include everything but the env and wasi modules, as it is the responsibility of the
# consumer of this library to define how and in what environment its artifact will run.

libenv.a is intentionally excluded from libbarretenberg.a because it provides environment-specific functions (logstr, throw_or_abort_impl, env_hardware_concurrency) that different consumers may need to implement differently (WASM vs native vs FFI).

So the current linking is:

• libbarretenberg.a - main library (excludes env/wasi by design)
• libenv.a - native environment implementation
• libvm2_stub.a - AVM recursion stub
• libstdc++ - C++ runtime (required for any C++ code)

Creating a single libbb-external.a that bundles everything is a good idea for the future, but would require CMake changes to create that combined archive.

[ludamad]

And why not cmake changes?

[johnathan79717]

And why not cmake changes?

You're right. I'm not sure what I was thinking. Done.

[ludamad]

LGTM now :)