While stress-testing #36147 I noticed sporadic port collisions still occurring on FreeBSD.
set_ephemeral_port_range() keeps the source port out of the test port range, but only for sockets the framework creates itself. Python's http.client creates its sockets internally, so RPC and REST connections can still be given a source port inside the test range. A connection to a closed port can then connect to itself. For example, the wrong-RPC-port startup check failed with BadStatusLine: POST / HTTP/1.1 because the client read back its own request.
This change adds a netutil.HTTPConnection subclass that sets the port range before connecting, and uses it in AuthServiceProxy and in the tests that open HTTP connections directly.
HTTPS is left unchanged because we don't serve RPC over TLS so it seems unnecessary.