Support ipv6 addresses in Tor Circuit DIsplay

Bridges and other nodes may have ipv6 addresses, and we need to fix the tor circuit display so that it handles these correctly.

added component::applications/tor browser owner::tbb-team priority::medium severity::normal status::new tbb-circuit-display tbb-usability type::defect labels

Trac:
Cc: N/A to mcs

Trac:
Description: Bridges and other nodes may have ipv6 addresses, and we need to fix the tor circuit display so that handles these correctly.

to

Bridges and other nodes may have ipv6 addresses, and we need to fix the tor circuit display so that it handles these correctly.

#17840 (moved) adds client support for bootstrapping and connecting to guards over IPv6. But Tor Browser shows the guard's IPv4 address, not the address that tor is actually connected to.

Trac:
Sponsor: N/A to N/A
Severity: N/A to Normal

#18584 (moved) is a duplicate.

Trac:
Reviewer: N/A to N/A
Cc: mcs to mcs, teor

#27954 (moved) is a duplicate.

Trac:
Cc: mcs, teor to mcs, teor, Parckwart

This issue confused a user on IRC today:

after some playing around with my tor browser bundle, I found I had to set ClientUseIPv6 to 1, and also set ClientUseIPv4 to 0. after doing that, despite TBB telling me IPv4 addresses in the circuit list, wireshark confirmed it was in-fact connecting over IPv6 :)

mentioned in issue #18584 (moved)

mentioned in issue #19843 (moved)

mentioned in issue #27954 (moved)

moved to tpo/applications/tor-browser#14939 (closed)

mentioned in issue tpo/applications/tor-browser#27954 (closed)