lnwire: remove stale pong limit error

Drop the unused pong limit decode error now that ping deserialization
accepts the full uint16 wire range. Update the randomized ping generator
to cover the full range so the property tests exercise the no-reply
sentinel values too.

Author: yyforyongyu

lnwire/pong.go

@@ -2,7 +2,6 @@ package lnwire
 
 import (
 	"bytes"
-	"fmt"
 	"io"
 )
 
@@ -11,10 +10,6 @@ import (
 // 2 bytes, leaving 65531 bytes.
 const MaxPongBytes = 65531
 
-// ErrMaxPongBytesExceeded indicates that the NumPongBytes field from the ping
-// message has exceeded MaxPongBytes.
-var ErrMaxPongBytesExceeded = fmt.Errorf("pong bytes exceeded")
-
 // PongPayload is a set of opaque bytes sent in response to a ping message.
 type PongPayload []byte
 

lnwire/test_message.go

@@ -1541,7 +1541,7 @@ var _ TestMessage = (*Ping)(nil)
 //
 // This is part of the TestMessage interface.
 func (p *Ping) RandTestMessage(t *rapid.T) Message {
-	numPongBytes := uint16(rapid.IntRange(0, int(MaxPongBytes)).Draw(
+	numPongBytes := uint16(rapid.IntRange(0, math.MaxUint16).Draw(
 		t, "numPongBytes"),
 	)