Add aggregation functions and tests

[silathdiir]

• Testing updates on servers.

Separate from PR #160

Summary

1. Add aggregator Prover and Verifier.

2. Add aggregation-tests.

3. Update zkevm-prove and zkevm-verify bin commands.

Test

• make test-inner-prove could pass.
• make test-chunk-prove could pass.
• make test-agg-prove could pass.
• bin/zkevm_prove and zkevm_verify could pass.

TODO (may fix in another PR)

• Current layer3-degree = 19, it cause layer4-degree = 25 and layer4-num-advice = 3, may need to update.
• the proof of inner circuit may be non deterministic #183

[lispc]

we must give evm proof to roller coordinator. Since it is the evm proof that is verified on chain. So we have 2 choice here

(1) give both evm proof and normal proof to roller coordinator, then the roller coordinator verifies normal proof, stores evm proof into db and later publish evm proof on chain
(2) give only evm proof to roller coordinator. the roller coordinator verifies evm proof, stores evm proof into db and later publish evm proof on chain. I recommand this way, but one thing i am concern is you regenerate YUL&BIN inside the Verifier::evm_verify. It may be slow. So i have several solution for this: (A) change pub unsafe extern "C" fn init_agg_verifier(params_dir: *const c_char, vk_path: *const c_char) to pub unsafe extern "C" fn init_agg_verifier(params_dir: *const c_char, vk_path: *const c_char, bytecode_bin_path: *const c_char) or pub unsafe extern "C" fn init_agg_verifier(params_dir: *const c_char, assets_dir: *const c_char), just load the BIN from disk instead regenerating it inside verifier (B) inside Verifier::new, create bytecode bin using gen_evm_verifier, the num_instance is in fact all the same, so just hard code it (C) cache deployment_code inside Verifier struct, inside Verifier::evm_verify, if deployment_code is None, generate and store it inside struct, if deployment_code is Some(xx), use it without regenerating.

btw inside roller coordinator, verification may be multi thread. So if we choose (C) above, we may need deployment_code: Arc<Mutex<Option<Vec<u8>>>?

[silathdiir]

we must give evm proof to roller coordinator. Since it is the evm proof that is verified on chain. So we have 2 choice here
...

Suppose to fix to fn init_agg_verifier(params_dir: *const c_char, assets_dir: *const c_char) and load both vk and bytecode BIN from assets_dir.