feat (batcher): allow users to specify max fee

[taturosati]

Users can now specify a max fee for a certain task. They sign this max fee, the contract then verifies that what the fee the batcher set * tx gas price is less than that max fee.

The batcher builds the batch putting the highest max fees first, but making it as big as possible without making it invalid (adding a fee that was too low).

The batcher also checks that a single user has not specified a bigger max fee for a bigger nonce, since this would cause the greater nonce to be sent first.

The batcher allows a user to replace a pending task by specifying the same nonce and a bigger fee. To prevent issues with this, the batcher checks that there is not a smaller nonce with a smaller fee (same as when adding a new task).

To send a task with a specific max_fee and nonce run in the batcher/aligned dir:

cargo run --release -- submit \
--proving_system Groth16Bn254 \
--proof ../../scripts/test_files/gnark_groth16_bn254_infinite_script/infinite_proofs/ineq_1_groth16.proof \
--public_input ../../scripts/test_files/gnark_groth16_bn254_infinite_script/infinite_proofs/ineq_1_groth16.pub \
--vk ../../scripts/test_files/gnark_groth16_bn254_infinite_script/infinite_proofs/ineq_1_groth16.vk \
--proof_generator_addr 0x66f9664f97F2b50F62D13eA064982f936dE76657 \
--private_key 0x4bbbf85ce3377467afe5d46f804f221813b2bb87f24d81f60f1fcdbf7cbf4356 \
--nonce 0 \
--max_fee 10000000000000

Note that if you don't specify a nonce it will fetch from disk cache / rpc and if you don't specify a max fee, it has a default.

Also note that you will need a funded account for this, since if not the batcher will just replace max fee and nonce. To fund that private key you can run:

cast send 0x7969c5eD335650692Bc04293B07F5BF2e7A673C0 --private-key 0x4bbbf85ce3377467afe5d46f804f221813b2bb87f24d81f60f1fcdbf7cbf4356 --value 100ether

[uri-99]

Should the Batcher close the first connection with a client if a proof is sent again with same nonce and bigger fee?
Its odd if a user has many open connections with the same nonce.

[uri-99]

Ser resolve TODO please

[uri-99]

Considering this PR adds informing different errors to the client (invalid fee, invalid nonce, etc), reverted txs should also be informed to the client

issue about this:
#919