lnd: use the default peer port when launching persistent conn goroutines
lnd: use the default peer port when launching persistent conn goroutines

This commit fixes a slight bug in the deamon. Previously we would store
the *net.TCPAddr that we observed when we either connected out to the
peer, or the peer connected to us. When making an outgoing connection
the host+port combination would be correct, but when responding to an
incoming connection, the port assigned after the TCP handshake would be
stored in the database. This would cause many goroutines to repeatedly
fail connections within the connmgr. Atm within the connmgr, it isn’t
possible to cancel requests for failed connection even after we’ve
already established a connection.

This commit fixes that issues by using the default peer port when
attempting to establish outbound connections to our channel peers.

aakselrod/lnd,LightningNetwork/lnd,AndrewSamokhvalov/lnd,ddustin/lnd,LightningNetwork/lnd,aakselrod/lnd,ddustin/lnd,AndrewSamokhvalov/lnd