Enhancement: Option to open admin & app ports on 0.0.0.0

[8e8b2c]

At the moment, the steps required to containerise a conductor such that it can be driven by another container include:

• opening an admin port at a fixed port (which forced to be on 127.0.0.1 loopback address)
• forwarding traffic from an exposed port of 0.0.0.0 to the above port (I use socat)
• repeating the same steps for the app port

This approach leads to confusing port mappings, and complicates a connection process that would normally be simpler were the client and conductor at the same network address. E.g. Opening an app port at runtime via AdminWebsocket::attach_app_interface is not practical because it would need to be coupled with some other convoluted tooling for forwarding and remapping.

[github-actions]

This item has been open for 30 days with no activity.

[github-actions]

This item has been inactive for 14 days since being marked as stale.