Add aggregation to merge/decider/translator recursive verifiers
This would involve modifying the verify_proof interfaces to take in an aggregation object and aggregating the pairing points from KZG.
The tube circuit would then have proper aggregation. (but that's set to change with much of the tube circuit going to Noir?)
Maybe none of this needs to be done except for the merge part, which needs to be handled through folding because we don't have a proof of correctness otherwise.
Unless we implement the Honk recursive verifiers using the Decider recursive verifier.
So yeah: we only need to do this for UH
@lucasxia01 please assess
I would think we need to do this for all three still. They all output pairing point objects that need to be accumulated. I'm not sure how difficult it would be to do for the merge verifier since that would be in the clientIVC side, but for the decider/translator, it should be pretty trivial to do.