[rocketmq-connect-runtime] client ip chosen from random local NIC ip address

The issue tracker is **ONLY** used for bug report and feature request.

Any question or RocketMQ proposal please use our [mailing lists](http://rocketmq.apache.org/about/contact/).

**BUG REPORT**

1. currently the consumer/producer client ip is choosen from random NIC ip address, which means if there are more than 1 non-local/loop-back NIC then the IP address could be anything (I once found the broker/consumer ip address the same as the docker0 bridge address)

2. As our client config synchronization relys on proper client ip address, we need to make client(consumer) ips configurable in connect runtime, or consider using a different mechanism.

The payload names no source file, test, or entry point. Start by locating client-IP selection and configuration in rocketmq-connect-runtime, then reproduce behavior with multiple non-loopback NICs including docker0; done means client IP selection is deterministic or configurable and client configuration synchronization remains reliable.

Written by the indexing model from the issue text.