[FEATURE] Support multiple listeners by using advertisedListeners

[wangjialing218]

Is your feature request related to a problem? Please describe.
Here provide a design for #574, could also be a solution for #633

Suppose we deploy kop with pulsar on a host which have two NIC, such as a cloud ECS. 192.168.1.10 is the address for private network inside the cloud and 172.16.1.10 is the address for public network.
We start pulsar endpoints at 6650, 6651 on both NIC for pulsar, and start endpoints at 9092, 9093, 19002, 19003 for kafka.

We would config like this for pulsar:

internalListenerName=pulsar_private
advertisedListeners=pulsar_private:pulsar://192.168.1.10:6650,pulsar_private_ssl:pulsar+ssl://192.168.1.10:6651,pulsar_public:pulsar://172.16.1.10:6650,pulsar_pulic_ssl:pulsar+ssl://172.16.1.10:6651

We would config like this for kafka:

listeners=PRIVATE://0.0.0.0:9092,PRIVATE_SSL://0.0.0.0:9093,PUBLIC://0.0.0.0:19002,PUBLIC_SSL:0.0.0.0:19003
advertised.listeners=PRIVATE://192.168.1.10:9092,PRIVATE_SSL://192.168.1.10:9093,PUBLIC://172.16.1.10:19002,PUBLIC_SSL:172.16.1.10:19003
listener,security.protocal.map=PRIVATE:PLAINTEXT,PRIVATE_SSL:SSL,PUBLIC:PLAINTEXT,PUBLIC_SSL:SSL

Kop current use kafkaAdvertisedListeners to config advertised address for kafka, but only support one address of one protocol.

Describe alternatives you've considered
Deprecated the setting kafkaAdvertisedListeners.
remove the function KafkaRequestHandler.getProtocolDataToAdvertise()
and config kop like this:

kafkaListeners=PRIVATE://0.0.0.0:9092,PRIVATE_SSL://0.0.0.0:9093,PUBLIC://0.0.0.0:19002,PUBLIC_SSL:0.0.0.0:19003
kafkaProtocalMap=PRIVATE:PLAINTEXT,PRIVATE_SSL:SSL,PUBLIC:PLAINTEXT,PUBLIC_SSL:SSL
advertisedListeners={pulsar's listeners},PRIVATE:pulsar//192.168.1.10:9092,PRIVATE_SSL:pulsar//192.168.1.10:9093,PUBLIC:pulsar//172.16.1.10:19002,PUBLIC_SSL:pulsar:172.16.1.10:19003

We should create four endpoints in this case mapped port with listenerName: PRIVATE:9092,PRIVATE_SSL:9093,PUBLIC:19002,PUBLIC_SSL:19003

When we receive a request from client, we get the listener name mapped with the endpoint which client connected to, use the listener name to do topic lookup and get the advertised address configed in advertisedListeners, get the protocal mapped with the listener name configed in kafkaProtocalMap, then we could generate the lookup response to client.

[willwinberg]

@BewareMyPower Did you mean to assign me to this?

[BewareMyPower]

@willwinberg Sorry it's my mistake, I just typed "w" and chose the false item

[EronWright]

A follow-up to this effort: #818