Refactor: BrokerPort should be configurable

[zyfdegh]

In communication/nats/discovery/config.go, broker port is currently hard-coding as

BrokerPort             = 4222

It impossible to change if broker (NATS) use a different port.

[Waldz]

Good idea, we could implement argument --broker-port save way as argument mysterium_server --broker-address=127.0.0.1 is implemented.

Feel free to contribute to our repo

[zyfdegh]

@Waldz Since -broker-address is address of broker, it's supposed to contain host and port. We can simply append the port in existing address. So I will put a PR later to parse the address and update the documents on how to use the flag and .env.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Waldz]

Service provider how can control broker-address - where his communication channel is.

myst help

--broker-address value           Address (IP or domain name) of message broker (default: "testnet-broker.mysterium.network")

I suggest to have contact.broker-address and contact.broker-port to have more control where communication channel is established