[Feature]: Bind Hoop Client to 0.0.0.0 or arbitrary address

[MartinLoeper]

Is your feature request related to a problem?

It would be helpful to have a config flag --expose for hoop login and hoop connect.
We want to start the hoop client via docker image and noticed that it binds to 127.0.0.1 instead of 0.0.0.0

Describe the solution you'd like

A config flag --bind or env variable BIND_ADDRESS for the socket bind of the oauth flow and the proxy which defaults to 127.0.0.1 but can be overwritten to 0.0.0.0. Alternatively a flag --expose which binds to 0.0.0.0

Describe alternatives you've considered

I am currently forwarding the data by using socat inside the container. I am listening on 0.0.0.0: and forward to 127.0.0.1: socat TCP4-LISTEN:3588,fork,reuseaddr TCP4:127.0.0.1:3587 with docker run -d -p 3587:3588 --name hoop hoophq/hoop:latest sleep 100000

Priority

Medium - Would improve my workflow

Use Case

We have a docker-compose setup where application containers would benefit of accessing hoop - running in a container itself. I do not understand why hoop binds to 127.0.0.1 by default which makes it difficult to implement container <-> container access.

Mockups or Examples

No response

Additional Context

No response

Contribution

• I would be willing to submit a PR to implement this feature

Code of Conduct

• I agree to follow this project's Code of Conduct