server: use chanInfo instead of chanPolicy to establish channel peer conns
server: use chanInfo instead of chanPolicy to establish channel peer conns

In this commit, we modify the way we attempt to locate the our channel
peer to establish a persistent connection on start up. Before this
commit, we would use the channel policy pointing to the peer to locate
the node as it's embedded in the struct. However, at times it's
currently possible for the channel policy to not be found in the
database if the remote nodes announces before we finalize the process on
our end. This can at times lead to a panic as the pointer isn't checked
before attempting to access it.

To remedy this, we now instead use the channel info which will _always_
be there if the channel is known.

LightningNetwork/lnd,aakselrod/lnd,aakselrod/lnd,LightningNetwork/lnd