fix: suppress debug assertions during mock IVC VK generation

The nightly barretenberg debug build fails in test_chonk_standalone_vks_havent_changed.sh
because BB_ASSERT_DEBUG(kernel_return_data_match) fires in chonk.cpp when using mock IVC
data for VK generation. The mock data has intentionally mismatched dummy calldata
commitments ({1, 2}) that don't match the kernel_return_data from proof public inputs.

Fix: use BB_DISABLE_ASSERTS() guard when processing HN recursion constraints with mock IVC
(ivc_base == nullptr), which is the VK generation path. These databus consistency checks
are only meaningful with real witness data, not the dummy values used during VK derivation.

Author: AztecBot

barretenberg/cpp/src/barretenberg/dsl/acir_format/recursion_constraint.cpp

@@ -251,6 +251,10 @@ void process_hn_recursion_constraints(
     // constraints present in the program. This is for when we write_vk.
     if (ivc_base == nullptr) {
         auto mock_ivc = create_mock_chonk_from_constraints(hn_recursion_data.first);
+        // Suppress debug assertions when using mock IVC data for VK generation. The mock data has
+        // intentionally mismatched dummy values (e.g. calldata commitments) that trigger databus
+        // consistency checks in chonk.cpp. These checks are only meaningful with real witness data.
+        BB_DISABLE_ASSERTS();
         process_with_ivc(mock_ivc);
     } else {
         auto chonk = std::dynamic_pointer_cast<Chonk>(ivc_base);