[Feature]: Optional bind address for CLI websocket server (-p flag)

Is there an existing issue for this?

• I have searched the existing issues

Platform

Linux

App version

v6.4.8.0

Feature

When running simplex-chat CLI in a Docker container with the -p flag for websocket server mode, the server binds to 127.0.0.1, making it inaccessible from outside the container.

Current workaround: Using socat to forward traffic from 0.0.0.0 to the localhost-bound websocket server.

Proposal: An optional flag (e.g., --ws-host) to specify the bind address for the websocket server. The default would remain 127.0.0.1 for security, with users explicitly opting in to bind to other addresses.

I've traced the code to runLocalTCPServer in simplexmq where the bind address is hardcoded. Happy to submit a PR if this approach is acceptable.

Start at runLocalTCPServer in simplexmq, where the issue says the websocket bind address is hardcoded, and trace how websocket server mode and the CLI -p flag reach it. Define the optional bind-address flag while preserving 127.0.0.1 by default, then verify that an explicitly supplied address allows access from outside a Docker container.