fix(codeql): drop mid/batid from buffer-cap debug log (PII)

CodeQL flagged the log message in OnMapTrace as 'Clear-text logging of
sensitive information' because the formatted tuple included mid/batid.
Same class of issue as the earlier d88f690 fix on this branch — only the
cap value is needed for diagnosis, the device identifiers are not.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: Beennnn

deebot_client/messages/json/map/__init__.py

@@ -330,10 +330,11 @@ def _handle_body_data_dict(  # noqa: PLR0911 - error-handling fan-out reads clea
         existing = cls._CHUNK_BUFFER.get(key, {})
         per_key_total = sum(len(b) for b in existing.values()) + len(chunk_bytes)
         if per_key_total > cls._MAX_BYTES_PER_KEY:
+            # Don't log mid/batid — those identify a specific account/device
+            # and CodeQL flags them as PII.
             _LOGGER.debug(
-                "onMapTrace: per-key buffer cap (%d B) exceeded for %s; dropping",
+                "onMapTrace: per-key buffer cap (%d B) exceeded; dropping",
                 cls._MAX_BYTES_PER_KEY,
-                key,
             )
             cls._CHUNK_BUFFER.pop(key, None)
             return HandlingResult.analyse()