Fix issues with running localproxy from docker image

[kareali]

Motivation

• Issue number: #43, #45
• fix #43 Adjust Openssl configuration script in Dockerfile: Using linux-generic64 configuration for openssl fails on some aarch64 chips (Apple M1 chip) when trying to use localproxy via docker causing the connection to get disrupted during the handshake so I'm switching to linux-aarch64 configurations when the architecture is aarch64.
• fix #45 Allowing localproxy source port exposure via docker : To forward traffic from the host machine to the docker container, we need to expose the listening port, and bind the localproxy listener to 0.0.0.0 address since "localhost" address is only accessible from within the container.

Modification:

Added new build flag to select whether to determine which IPV4 address localproxy should bind to and updated the docker-run.sh script to accept a port as an argument.

Testing

• 43 test: Using an arm64 machine with Amazon Linux 2 installed, I ran localproxy from docker and had the user who created the issue test the fix on their machine.

• 43 test:

  1. Ran the localproxy using docker, confirmed it's binding to 0.0.0.0 and that I can SSH from outside the container (the host).
  2. Ran the localproxy natively, confirmed it's binding to localhost and that I can SSH from the host.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.