Hot Rod needs proxy address and port to work on cloud-like envs

To get HotRod to work properly on environments such as ec2, a configurable proxy host+port are needed.

Example:

• Hot Rod running on an ec2 instance with elastic IP address 1.2.3.4
• If you bind to 0.0.0.0, Hot Rod server starts and serves requests via 1.2.3.4, but the exposed address in the topology is 0.0.0.0. Hence, client fails to connect to 0.0.0.0.
• You can't have the Hot Rod bind to 1.2.3.4 since it does not exist in the ec2 instance.
• So, a proxy address and port are needed so that these are published in topology views to external clients.