trigger failover endpoint switching when FetchError or any Error is thrown

[rampall]

Sep 19 17:48:53 test-server etherproxy[33254]: Cache hit: https://go.getblock.io/84****************************48_{"jsonrpc":"2.0","method":"web3_clientVersion"}
Sep 19 17:48:53 test-server etherproxy[33254]: Cache hit: https://go.getblock.io/84****************************48_{"jsonrpc":"2.0","method":"web3_clientVersion"}
Sep 19 17:48:53 test-server etherproxy[33254]: Cache hit: https://go.getblock.io/84****************************48_{"jsonrpc":"2.0","method":"web3_clientVersion"}
Sep 19 17:48:59 test-server etherproxy[33254]: Key: https://go.getblock.io/84****************************48_{"jsonrpc":"2.0","method":"web3_clientVersion"}
Sep 19 17:48:59 test-server etherproxy[33254]: FetchError: invalid json response body at https://go.getblock.io/84****************************48 reason: Unexpected token 'O', "Out of CU" is not valid JSON
Sep 19 17:48:59 test-server etherproxy[33254]:     at /home/user1/.nvm/versions/node/v20.17.0/lib/node_modules/etherproxy/node_modules/node-fetch/lib/index.js:273:32
Sep 19 17:48:59 test-server etherproxy[33254]:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
Sep 19 17:48:59 test-server etherproxy[33254]:   type: 'invalid-json'
Sep 19 17:48:59 test-server etherproxy[33254]: }
Sep 19 17:48:59 test-server etherproxy[33254]: Cache hit: https://go.getblock.io/84****************************48_{"jsonrpc":"2.0","method":"web3_clientVersion"}
Sep 19 17:48:59 test-server etherproxy[33254]: Cache hit: https://go.getblock.io/84****************************48_{"jsonrpc":"2.0","method":"web3_clientVersion"}
Sep 19 17:48:59 test-server etherproxy[33254]: Cache hit: https://go.getblock.io/84****************************48_{"jsonrpc":"2.0","method":"web3_clientVersion"}