Surface RPC error in trace

[ipatka]

Rather than assuming a rate limit error, return the error message from the RPC node

This far from perfect as it doesn't account for other error cases. Ideally we could pattern match to find the exact error case but different RPC providers return diff error formats. But I think this is potentially more helpful when debugging dataset requests

ex.

Alchemy

RETH with traces disabled

Before this PR:

TODOs

• Add similar error handling to other dataset files

[sslivkoff]

awesome this is very useful to have