Update HashIO to point to random CNs

[Nana-EC]

Problem

Currently HashIO points to a single CN.
However utilizing the SDKs random selection of nodes would be more appropriate

Solution

Utilize SDK random node allocation but also explore redundancy and latency considerations

Alternatives

No response

[quiet-node]

After a two-day observation of the update directing the mainnet Relay to random and multiple consensus nodes, no significant performance degradation was detected across the Consensus Nodes. Any metric variations were minor and likely due to normal traffic fluctuations.
• Reduced Memory Usage: Memory usage consistently decreased, with a 3.73% reduction on Day 1 and 6.88% on Day 2, indicating improved request distribution efficiency.
• Slight Increase in CPU Usage: CPU usage increased by 2.86% by Day 2, but remained within acceptable operational limits.
• No Node Degradation: All monitored nodes operated normally, with no signs of resource exhaustion or unexpected behavior.
• Stable Latency & No Failures: The eth_sendRawTransaction latency stayed within the expected range, and the failure rate remained at 0%, confirming no errors were introduced.

Overall, the update successfully distributed requests across multiple CNs without compromising system reliability or performance.