Feature Request: add an option to control which address to bind to for `tunnel:open`

[demosdemon]

ZD45776 https://github.com/platformsh/platformsh-cli/blob/a2ed37839800ede6e76413542f99bd8abbe26290/src/Command/Tunnel/TunnelCommandBase.php#L222-L239

from man 1 ssh:

 -L [bind_address:]port:host:hostport
 -L [bind_address:]port:remote_socket
 -L local_socket:host:hostport
 -L local_socket:remote_socket
         Specifies that connections to the given TCP port or Unix socket
         on the local (client) host are to be forwarded to the given host
         and port, or Unix socket, on the remote side.  This works by
         allocating a socket to listen to either a TCP port on the local
         side, optionally bound to the specified bind_address, or to a
         Unix socket.  Whenever a connection is made to the local port or
         socket, the connection is forwarded over the secure channel, and
         a connection is made to either host port hostport, or the Unix
         socket remote_socket, from the remote machine.

         Port forwardings can also be specified in the configuration file.
         Only the superuser can forward privileged ports.  IPv6 addresses
         can be specified by enclosing the address in square brackets.

         By default, the local port is bound in accordance with the
         GatewayPorts setting.  However, an explicit bind_address may be
         used to bind the connection to a specific address.  The
         bind_address of ``localhost'' indicates that the listening port
         be bound for local use only, while an empty address or `*' indi-
         cates that the port should be available from all interfaces.

The tunnel:open command currently does not allow you to specify the bind address; the default of which is subject to the GatewayPorts setting in the various ssh config files. The user would like to specify a custom bind address, such as * or 0.0.0.0 to explicitly allow outside devices to access the tunnel.