Chutney tests for IPv6-only bridge clients

I think this is working already, but we should check that chutney bridge clients are using IPv6, and not falling back to IPv4.

added component::core tor/chutney in Legacy / Trac ipv6 in Legacy / Trac outreachy-ipv6 in Legacy / Trac parent::17011 in Legacy / Trac points::1 in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::assigned in Legacy / Trac type::defect in Legacy / Trac labels

Setting ClientUseIPv4 0 should do this, but we should actually check we're connecting over IPv6.

We should also test with:

ClientUseIPv6 1
ClientPreferIPv6ORPort 1

and

ClientUseIPv6 1
ClientPreferIPv6ORPort 0

in combination with the IPv4 and IPv6 bridge lines, and only an IPv6 bridge line (this will likely require more chutney config variables that say "emit IPv4 bridge lines" and "emit IPv6 bridge lines", both defaulting to true).

Trac:
Component: Core Tor/Tor to Core Tor/Chutney
Owner: N/A to teor

Trac:
Sponsor: N/A to SponsorV-can

Trac:
Owner: teor to N/A
Status: new to assigned

Make everything that is assigned to no-one new again.

Trac:
Status: assigned to new

Removing sponsor V as we do not have more time to include this tickets in the sponsor.

Removing sponsor from tickets that we do not have time to fit in the remain of this sponsorship.

Trac:
Sponsor: SponsorV-can to N/A

Trac:
Keywords: N/A deleted, outreachy-ipv6 added

Trac:
Owner: N/A to MrSquanchee
Status: new to assigned

We haven't selected a GSOC or Outreachy applicant yet.

To be fair to all applicants, we should only assign tickets to people who are actively working on that ticket.

Trac:
Owner: MrSquanchee to N/A

changed time estimate to 8h

moved from legacy/trac#20068 (moved)

added Bug label and removed 1 deleted label

added IPv6 label and removed 1 deleted label

Not currently in scope, but it would be nice if we did it.

added First Contribution label

removed Bug label

added Icebox label