Split KLAP IoT updates into smaller requests and validate KLAP responses (#1829)

Some IoT devices respond over KLAP with a plain `200 OK` html page
instead of a proper response when the response would be too large to
construct, causing a "not a multiple of the block length" decryption
error (e.g., KS200M in #1828).

This PR lowers the maximum response size to 2048 bytes for IoT devices
using KLAP, so that the update is split into multiple smaller requests
like it is already done for bulbs.

In details:
- `IotDevice.max_device_response_size` returns 2048 over KLAP. Bulbs
  keep 4096 and XOR devices keep 16 KiB.
- `KlapTransport` checks the response length and signature before
  decrypting, and raises a `KasaException` telling what was wrong
  instead of the decryption error.

Fixes #1828

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

kasa/iot/iotdevice.py

@@ -24,7 +24,7 @@ from warnings import warn
 
 from ..device import Device, DeviceInfo, WifiNetwork
 from ..device_type import DeviceType
-from ..deviceconfig import DeviceConfig
+from ..deviceconfig import DeviceConfig, DeviceEncryptionType
 from ..exceptions import KasaException, TimeoutError, UnsupportedDeviceError
 from ..feature import Feature
 from ..module import Module
@@ -730,6 +730,11 @@ class IotDevice(Device):
     @property
     def max_device_response_size(self) -> int:
         """Returns the maximum response size the device can safely construct."""
+        # Over KLAP, some devices answer a request whose response would be
+        # larger than about 4 KiB with a plain html page instead of a response,
+        # and have even less room right after a state change.
+        if self.config.connection_type.encryption_type is DeviceEncryptionType.Klap:
+            return 2048
         return 16 * 1024
 
     @property