feat: add Q10 map management controls

[hCoureau]

Important

Depends on #933 (and transitively #932). Please do not merge this PR until #933 has landed; this branch currently includes those commits and will be rebased onto main afterwards.

Related to #767. #908 owns current position, zoned cleaning, and goto; this PR does not duplicate those APIs. The common-coordinate point introduced here follows the maintainer feedback on #908 and is intended to be reused there.

Summary

• expose typed no-go, no-mop, threshold, and virtual-wall data in common Roborock millimetre coordinates
• add atomic full-collection setters for restricted zones and virtual walls
• add reversible room rename and saved-map apply controls
• keep device pushes authoritative instead of mutating cached map state after a publish
• preserve unknown restriction type bytes and refuse unsafe replacement when the device snapshot is missing, malformed, or contains an unsupported polygon shape

Protocol and safety

Binary packing lives in the B01 protocol layer. Public APIs accept structured immutable points, restrictions, and walls rather than base64 or raw Q10 vector units. Coordinates must align to the device's 5 mm vector grid and fit signed 16-bit wire values.

Restriction and wall writes replace the entire stored collection. The restriction setter therefore requires a complete, representable DP 55 snapshot before publishing. Invalid geometry, duplicate points, unsupported cardinality, invalid types, overflow, and excessive collection sizes fail before any command is sent.

Saved-map apply remains asynchronous and does not optimistically alter the cached map list. The existing select operation remains preview-only.

Validation

• uv run pytest -q: 1127 passed, 89 snapshots passed
• uv run pre-commit run --all-files: passed, including Ruff, mypy, codespell, structured-file checks, and private-key detection
• uv build: passed repeatedly for both sdist and wheel
• byte-exact encoder tests cover real multi-zone and mixed-orientation wall captures, canonical empty payloads, signed boundaries, unknown type preservation, and caller immutability
• validated on a physical Q10 S5+: applied and observed a temporary no-go zone, virtual wall, and room rename; restored every original value and verified the robot remained docked/charging
• exercised saved-map apply and readback safely; this device currently has one saved map, so a cross-map transition was not available to test
• installed the exact final wheel into local Home Assistant and verified integration startup plus a complete live map image with no new integration/backend errors

No credentials, identifiers, personal room labels, floorplans, or private packet captures are included.

Deliberate exclusions

• room split/merge and map delete/reset are destructive and were not tested on the primary household map
• map rename lacks a fully captured request shape on this firmware
• per-room repeat, route, fan, and mop settings remain a separate cleaning-controls contribution pending one-factor-at-a-time captures
• current position, zoned cleaning, and goto remain in feat: add Q10 zone, position, and goto support #908

Reviewer guide

1. Q10RoborockPoint and overlay models: public coordinate/type boundary
2. B01 protocol encoders: framing, geometry validation, range checks, and fixed room-name field
3. Q10 map traits: snapshot safety, exact COMMON envelopes, and push-authoritative state
4. protocol and trait tests: real captures, malformed inputs, no-publish failures, and replacement semantics

[hCoureau]

On hold following the review feedback on #933: please do not review the current cumulative diff.

Once the read-only map stack lands, this draft will be rebased and repartitioned into focused changes:

1. common-coordinate points plus typed/read-only restriction and wall models
2. restricted-zone and virtual-wall encoders/replacement setters
3. room rename and saved-map apply controls

Each part will be submitted sequentially against main, with its own focused tests and reviewer guide.

[lboue]

@hCoureau This branch has conflicts that must be resolved.

[hCoureau]

Resolved the merge conflicts with current main in 24002af by merging main and retaining its accepted 30-second Q10 CLI map-push timeout. The map-management changes are preserved. GitHub now reports this PR as conflict-free, and I marked it ready for review.

Validation: 1,150 tests passed, 92 snapshots passed, all pre-commit hooks passed, and sdist/wheel builds passed. GitHub CI was triggered for the new head. Required maintainer approval still applies.

#933 has already merged. This branch still contains the stacked Q10 archive/obstacle/current-room work, which remains visible for maintainer review. Conflict resolution and validation performed with OpenAI Codex assistance.