[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

Beginne damit, die firehose-Verbindung von graph-node nachzuverfolgen und zu untersuchen, wie sie DNS-Namen behandelt, die in mehrere IPv4- und IPv6-Adressen aufgelöst werden. Reproduziere das Verhalten mit einem DNS-Ergebnis mit mehreren Adressen oder untersuche es, einschließlich in einer Umgebung ohne IPv6. Als erledigt gilt, wenn verfügbare Adressen der Reihe nach ausprobiert werden, statt bei einer einzigen IPv4-Adresse hängen zu bleiben.