Pass both hostname and port into SSLClientSocket

Pass both hostname and port into SSLClientSocket

This fixes various TODOs regarding not passing a port along with a hostname.
Most notably, host_and_port in SSLCertRequestInfo now actually contains the
port. We also appropriately include it in the SSL peer ID on OS X.

This does result in some UI change, in that we now display the port on
certificate selection dialogs. We should probably display the EV name, but we
cannot verify certificates early enough for now.

BUG=none
TEST=none

Looks like someone else beat me to it.
http://codereview.chromium.org/4339001

[davidben, 2010-08-11 23:31:19]

This unfortunately touches a lot of files, as we create SSL sockets in a tons of
places.

(Pawel: it looks like this conflicts uninterestingly with your testserver CL.
Don't worry about it; I'll let you go first and rebase mine when it lands.)

[davidben, 2010-08-12 05:58:15]

Well, try bots suggest I missed a few...

I think I have a better idea though. Instead of essentially duplicating the port
information and requiring everyone who creates an SSLClientSocket to supply that
duplication, what if we add a GetEndpointAddress method to ClientSocket?
SSLClientSocket can just pull the port out of there without fear of proxy
problems.