feat: add max_decoding_message_size config

[GCdePaula]

@gligneul can you test with the node and check if this solves the message size issue?

[gligneul]

I set the value to 104857600. (It can be confirmed in the logs.)

rollups-examples-state_server-1  | 2023-09-11T14:56:51.585386Z  INFO cartesi_rollups_state_server: starting state server config=StateServerConfig { state_fold: SFConfig { concurrent_events_fetch: 16, genesis_block: 1, query_limit_error_codes: [], safety_margin: 1 }, block_history: BHConfig { ws_endpoint: "ws://hardhat:8545", http_endpoint: "http://hardhat:8545", block_timeout: 8s, max_depth: 1000 }, server_address: 0.0.0.0:50051, max_decoding_message_size: 104857600 }

And the error still happens after the first input. Maybe we need to change the client side as well?

rollups-examples-dispatcher-1  | Error: StateServerError { source: TonicError { context: "`get_state` request", source: Status { code: OutOfRange, message: "Error, message length too large: found 5710040 bytes, the limit is: 4194304 bytes", metadata: MetadataMap { headers: {"content-type": "application/grpc", "date": "Mon, 11 Sep 2023 14:58:11 GMT"} }, source: None } } }

[gligneul]

@GCdePaula I tested it with examples, and it worked!

[gligneul]

@GCdePaula I thought again, and it might be better to set the default to 100 MB so we can avoid configuring these manually for the time being.

[gligneul]

I broke the node with an input of 500Kb; with Guilherme's estimation, it is just ~$100. cartesi/rollups-contracts#77

[GCdePaula]

Done!