tealdbg: listen on specified address

[algorandskiy]

Summary

Fix for #1809

Test Plan

Updated tealdbg e2e test

[tsachiherman]

How's about replacing it with an endpoint, so it would be more consistent with the rest of the platform ? I know that it will break backward compatibility though..

[algorandskiy]

--remote-debugging-port is here to have chrome-like option so that one can use VSCode's CDT plugin to drive debugging and have VSCode as UI.

[fabrice102]

I have checked on macOS. This worked for me by doing the following:

1. open the port 9392 in sandbox in Dockerfile.yml
2. inside sandbox (./sandbox enter algod), run:

   tealdbg debug --remote-debugging-port 9392 --listen "" a.teal

3. visit devtools://devtools/bundled/js_app.html?experiments=true&v8only=false&ws=127.0.0.1:9392/7d35cd8846288e164178efed7123a00efd0af5d906fed89b1c42fcc7593e3a7d instead of the URL displayed by tealdbg (i.e., adding 127.0.0.1 after ws=)

Note: I've tried to use the IP address 172.18.0.3 of the container instead of "" for listen (IP got by docker inspect -f '{{.Name}} - {{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' algorand-sandbox-algod, that matches ifconfig inside the sandbox docker container). This works when visiting devtools://devtools/bundled/js_app.html?experiments=true&v8only=false&ws=127.0.0.1:9392/7d35cd8846288e164178efed7123a00efd0af5d906fed89b1c42fcc7593e3a7d but not when visiting devtools://devtools/bundled/js_app.html?experiments=true&v8only=false&ws=172.18.0.3:9392/7d35cd8846288e164178efed7123a00efd0af5d906fed89b1c42fcc7593e3a7d, things seem to work but the source code does not appear.
So I don't know.

TLDR: Improve significantly the current state of the art. People need to manually fix the URL displayed by tealdbg, but it's quite painless. And fixing that in the code seems complex and not necessary.