Block catchup for some JSON/RPC providers requires custom evmconnect configuration

[matthew1001]

A discord discussion (https://discord.com/channels/905194001349627914/1128993021770354728/1128994332150607952) highlighted the fact that it is relatively easy to hit the maximum block request size for some JSON/RPC providers (Alchemy in the case of the above discussion).

One repercussion is that token pool can be left showing incorrect balances due to FireFly being unable to download old blocks (using eth_getLogs). The error message received from Alchemy by evmconnect is Response size is larger than 150MB limit.

The default number of blocks evmconnect requests is 500. The user who reported the issue ^^ said that it needed reducing to 25 in order for FireFly to be able to start the process of catching up with the chain.

It can involve some fairly time-consuming debugging on the part of the user and/or FireFly community to help users identify that this is the reason their token pools aren't showing correct data. It would be good if evmconnect recognised certain types of error case and automatically reduced the (in-memory) value for catchupPageSize until it started receiving blocks.

This won't avoid the slow catch-up time that a low catchupPageSize will cause, but it should mean that the user avoids having to debug what is likely to be a fairly common situation with 3rd party JSON/RPC providers.

[matthew1001]

Possibly related to hyperledger/firefly-evmconnect#26 but they error messages seen in the 2 cases are different

[matthew1001]

Fixed by hyperledger/firefly-evmconnect#106