Automate tracing Chonk VK changes down to low-level primitives

Our `test_chonk_standalone_vks_havent_changed` script captures high-level VK changes. It would be great to know what exactly has caused those changes. A step in this direction was taken in https://github.com/AztecProtocol/aztec-packages/pull/18499, where we pinned down all opcode gate counts. However, these tests won't capture subtle vk changes that don't affect gate counts. 