fix: batcher sends proof even if eip712 signature contents are incompatible

[uri-99]

This PR

There was a bug that the batcher accepted a proof if incompatible --chain and --batcher-payments-address where provided, which resulted in an Ethereum tx revert for the whole batch submition.

Resolving this, it was found that these 2 parameters where redundant, so they were both removed and replaced for the --network , which accepts either devnet, holesky-stage or holesky .

Then, this parameter is used by the SDK to the appropriate contract addresses, while the chainId is resolved from the RPC (this has not changed, which also lead to confusion).

To Deploy

• As the SDK changes with this PR, a new release with a new tag should be made (maybe v0.7.1 or v0.8.0)
• The Batcher should be redeployed, since a new check is being made
  • if client_msg.verification_data.payment_service_addr != self.payment_service.address() {
• The task sender should be restarted using this new parameter (make targets have been migrated)

To Test

You can test the new task senders, the batcher works correctly, and the examples

[entropidelic]

should we leave this version commit?

[uri-99]

The version should be the current one. Should I point it to the current branch? If i point it to an existing release, it won't contain the changes made in this PR

[entropidelic]

yes you are right. Let's make it point to the last commit of this branch, but we have to remember to update it once we make a release

[MauroToscano]

Why is it not using the repository version ? I assume we may want to keep them working while operators upgrade maybe ?

[uri-99]

The actual content of the requests does not change so the examples should be usable even before the SDK is released, right?

[entropidelic]

aside from some nits, code looks good and worked correctly