[Bug] Review reconnect logic for firehose

Bug report

When graph-node connects to firehose it may be provided a DNS name that resolves to multiple IPv4 and/or IPv6 addresses.

graph-node should explicitly try each of these available addresses. Of course if IPv6 is not configured in the networking stack, it would not try those. But if there are multiple IPv4 addresses, it should try each one in turn.

It appears, anecdotally, that graph-node does not specifically rotate between IPv4 addresses returned and gets stuck connecting to a single IPv4 address.

There are no logs for this, it is based on observed behaviour.

Relevant log output

No response

IPFS hash

No response

Subgraph name or link to explorer

No response

Some information to help us out

• Tick this box if this bug is caused by a regression found in the latest release.
• Tick this box if this bug is specific to the hosted service.
• I have searched the issue tracker to make sure this issue is not a duplicate.

OS information

None

首先跟踪 graph-node 的 firehose 连接，以及它如何处理解析为多个 IPv4 和 IPv6 地址的 DNS 名称。使用包含多个地址的 DNS 结果重现或检查行为，包括没有 IPv6 的环境。完成的标准是依次尝试可用地址，而不是一直卡在某一个 IPv4 地址上。