Streams: advertise localhost to local clients

[michaelklishin]

Note that there is a way to opt out just in case.

Closes #9424.

[acogoluegnes]

This is not working as expected, as the changes apply only to the hostname and port information carried out by the client connection, not where the information is actually advertised (which is in the metadata command).

We would need to make the same check and skip the remote calls to always return the information from the local node. This assumes there's only one node in the cluster.

With the current changes, the broker returns the hostname, e.g. foobar, the client connects to foobar, the connection information contains localhost, this is not what the client expects, so it closes the connection, and retries. Infinite loop.

[michaelklishin]

Instead of updating this PR to make the same change in two places we decided to try a client library solution. The downside of that is that we have to do it N times but the consensus on the team seems to be tilted that way.

[michaelklishin]

rabbitmq/rabbitmq-stream-java-client#420 is the first client library change that accomplishes the same goal.