add support for custom p2p node listen maddrs and dht announce maddrs

[mintyleaf]

Long story short - i'm trying to join multiple LocalAI nodes which is hosted as docker container images on the vast.ai hosting.
The problem is - you can't provide the network_mode: host in that environment.
The maximum you can do is expose some port locally for the container, and then the vast.ai service will remap it to some random port on public accessed machine address, like:

[ip4]:13371 -> 8090/tcp

To work around that i need to provide to the libp2p the address that is exposed locally to listen to using introduced flag --listen-maddrs "/ip4/0.0.0.0/tcp/8090"
After that, with some patience, using defaults, the node can be actually accessed through the power of auto relay (based on pure luck)

But we can push that further by announcing on DHT the real public rerouted address using another introduced flag --dht-announce-maddrs /ip4/[ip4]/tcp/13371

Combined both approaches we can successfully reach the node by it's public address right after discovery on the DHT.

The petals project is using the same approach: https://github.com/bigscience-workshop/petals/blob/22afba627a7eb4fcfe9418c49472c6a51334b8ac/src/petals/cli/run_server.py#L54

[JackBekket]

I do support this PR, we definetly need this thing to be able to connect nodes from standard enviroment and vast.ai

[mudler]

Looking good, thank you!

[JackBekket]

@mudler
Can you add it to local-ai and release new version?