Option to throw Exceptions on 404, and/or publish supported chains in an API call #41
Description
In my programs where I might use Envio, I am typically traversing 22 different chains. Making requests to Envio for unsupported chains (for instance, Cronos at 25.hypersync.xyz) simply prints internal retry errors rather than raising an Exception that I can then skip.
I don’t believe there’s an API call or other repository of enabled networks that would allow me to do this more intelligently, but I'd also rather not hardcode available networks, especially as Envio scales over time.
There's a max_num_retries on the ClientConfig, but that is too generic and could skip a query that might otherwise work after a single transient issue.
It would be great to have a setting that raises an Exception on 404.
It would also be helpful to get a list of supported networks - similar to your page on https://docs.envio.dev/docs/HyperSync/hypersync-supported-networks - in a consumable format.