peer: set HtlcPoint to nil within logWireMessage

This new field was added as a recent modification to the spec, but the
curve parameter within the attribute wasn’t set to nil. As a result
this would result in a large degree of spam within the logs when set to
trace mode. This commit fixes this issue by setting it to nil along
with all the other pub keys within messages.

peer.go

@@ -947,12 +947,14 @@ func (p *peer) logWireMessage(msg lnwire.Message, read bool) {
 		m.RevocationPoint.Curve = nil
 		m.PaymentPoint.Curve = nil
 		m.DelayedPaymentPoint.Curve = nil
+		m.HtlcPoint.Curve = nil
 		m.FirstCommitmentPoint.Curve = nil
 	case *lnwire.OpenChannel:
 		m.FundingKey.Curve = nil
 		m.RevocationPoint.Curve = nil
 		m.PaymentPoint.Curve = nil
 		m.DelayedPaymentPoint.Curve = nil
+		m.HtlcPoint.Curve = nil
 		m.FirstCommitmentPoint.Curve = nil
 	case *lnwire.FundingLocked:
 		m.NextPerCommitmentPoint.Curve = nil