Remove exception when reciveing large RCON packets

It does not make sense to throw an exception because the server sends
a too large response. While technicaly it breaks the spec, we can handle it
gracefully and it works better than the old Multi Packet RCON tricks.
Thanks @arildboifot for letting me know!
Relates to: #45

src/CoreRCON/PacketFormats/RCONPacket.cs

@@ -41,7 +41,6 @@ internal static RCONPacket FromBytes(byte[] buffer)
         {
             if (buffer == null) throw new NullReferenceException("Byte buffer cannot be null.");
             if (buffer.Length < 4) throw new InvalidDataException("Buffer does not contain a size field.");
-            if (buffer.Length > Constants.MAX_PACKET_SIZE) throw new InvalidDataException("Buffer is too large for an RCON packet.");
 
             int size = BitConverter.ToInt32(buffer, 0);
             if (size > buffer.Length - 4) throw new InvalidDataException("Packet size specified was larger then buffer");