fix(batcher): Update Lambdaworks Merkle Trees + Update merkle leaves length check in batcher

[PatStiles]

closes#970

• Updates the lambdaworks merkle tree dependencies in aligned layer from v0.7.0 -> v0.10.0.
• Updates the length check in the batcher to allow batches of size 1

Testing:

Test local testnet as expected and confirm no errors are emitted.

make deps

make install_aligned_compiling

make anvil_start_with_block_time

make aggregator_start

make operator_register_and_start

make batcher_start_local

make batcher_send_burst_groth16

Note:

I removed the padding of the merkle root leaves as specified in #979 . However, this caused the Tx to revert in the BatcherPaymentService contract with InvalidMerkleRoot error (after removing the leaves power of two check). Since the merkle tree verification was sourced from eigen https://github.com/code-423n4/2023-04-eigenlayer/blob/main/src/contracts/libraries/Merkle.sol#L129 my intuition is its failing due an invariant the leaves are a power of 2 therefore we need to preserve padding the leaves to a power of two. Removing the padding will be done in a separate pr.

[entropidelic]

When submitting a batch with only one proof, I am getting

Transaction reverted "0x9f13b65cfc222438ea0a6d0738343dfbd7ebd0aaf7a0cbfe1ef69f905eb2bbb6b3dfc6035c58ee0f5eb4cd6f6d30536add1a16cddd8fef8f334968b221c8d45eaf604219"

Which corresponds to the InvalidMerkleRoot error of the BatcherPaymentSercvice.sol contract

[uri-99]

Blocking PR until lambdaworks is fixed to allow merkle trees of size 1

[uri-99]

Seems to be working fine when pointed to latest commit of LambdaWorks. Waiting to see if a release will be done or if we should point to the latest commit efd46f0b0aea3aa95d94bba7de86cb96611b40d3
(probably the former)

[MarcosNicolau]

Code looks good, everything worked fine on my machine!

[uri-99]

still works

[Oppen]

Seems to be working fine when pointed to latest commit of LambdaWorks. Waiting to see if a release will be done or if we should point to the latest commit efd46f0b0aea3aa95d94bba7de86cb96611b40d3 (probably the former)

I can make a release if we need one. I'll talk with @diegokingston and @MauroToscano.