[Bug] Incorrect broker address assigned as 127.0.0.1 in K8s deployment

[chi3316]

Before Creating the Bug Report

• I found a bug, not just asking a question, which should be created in GitHub Discussions.

• I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.

• I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

Ubuntu 22.04
Kubernetes Cluster: Running on ACK

RocketMQ version

Branch: develop
Version: 5.3.1-SNAPSHOT

JDK Version

OpenJDK 8

Describe the Bug

In a Kubernetes environment, the RocketMQ Broker's address is incorrectly assigned as 127.0.0.1. This issue arises due to the getLocalInetAddress method in NetworkUtil, where loopback addresses are not excluded when traversing the localInetAddressList. As a result, when all IP addresses are internal, the method may incorrectly return 127.0.0.1

Steps to Reproduce

1. Deploy RocketMQ in a Kubernetes cluster.
2. Start the RocketMQ Broker.
3. Check the registered Broker address in the NameServer using the clusterList command.

What Did You Expect to See?

The Broker address should be a valid non-loopback IP address corresponding to the network interface within the Kubernetes environment.

What Did You See Instead?

The Broker address was incorrectly assigned as 127.0.0.1.

Additional Context

No response