New refactored RPC helpers that support web3.py v6 have introduced Eth price fetch failures

[muku314115]

Describe the bug

Bug :
| ERROR | RPC ERROR failed to fetch ETH price, error_msg:list index out of range| {'module': 'Powerloom|Snapshotter|SnapshotUtilLogger'} pooler_1 | 0|process-hub-core | April 18, 2024 > 09:36:49 | ERROR | RPC ERROR failed to fetch ETH price, error_msg:list index out of range| {'module': 'Powerloom|Snapshotter|SnapshotUtilLogger'} pooler_1 | 0|process-hub-core | April 18, 2024 > 09:36:49 | ERROR | RPC ERROR failed to fetch ETH price, error_msg:list index out of range| {'module': 'Powerloom|Snapshotter|SnapshotUtilLogger'}

Eth price fetch failures cause a complete halt on all snapshotting, this bug is uncommon but can persist for multiple epochs if left unchecked.

To Reproduce

Steps to reproduce the behavior:

1. Remote instance to be used - 143.198.177.25
2. cd powerloom
3. cd deploy
4. ./build-dev.sh

Expected behavior
After an epoch is released, snapshot building should commence and this error should pop up (it may require a few epochs)
snapshot submissions may fail but all those errors can be ignored as a complete setup is required to run this e2e

Proposed Solution
Appropriate exception handling and retry strategies to ensure the fetches finally go through as often as possible so as to not block the snapshot builds because of their dependency on ETH to USD price conversion.

Caveats
Working under the assumption the above error was introduced by the new RPC helpers that support web3.py v6

Additional context
Add any other context about the problem here. (e.g. OS, Python version, ...)