feat: compose Q10 maps in a pure renderer

[tubededentifrice]

Summary

Next PR in the #848 split, following #881 and #884. This adds the pure Q10 map-composition layer on top of the merged low-level decoding and cleanup work.

Source lifecycle and API

render_q10_map accepts the three independently updated source snapshots plus static config:

• Q10MapPacket — latest 01 01 map-protocol response; owns grid layers, header calibration, rooms, and erase zones.
• Q10TracePacket | None — latest 02 01 trace-protocol response; owns path points, robot position, and heading.
• Q10MapOverlays — latest decoded restricted-zone and virtual-wall snapshot from DPS.
• B01Q10MapParserConfig — static parser/render configuration.

It returns one fully composed PNG. Calibration, layers, projected MapData, and drawing state remain internal; there is no separate Q10MapRender data model or alternate draw_path_on_map image path.

Changes

• Derive calibration internally from the map and trace packets.
• Apply erase zones before rasterization.
• Project and draw trace path/position/heading and DPS overlays in one render operation.
• Keep all calibration, placement, and pixel work out of device traits.
• Cover the source boundary and observable image behavior directly in map-module tests.

This PR intentionally contains no device-trait, subscription, or CLI orchestration changes. Those remain in the next stacked PR.

Validation

• Focused map suite — 73 passed
• pytest -q — 790 passed, 86 snapshots passed
• pre-commit run --show-diff-on-failure --color=always --all-files — all hooks passed, including ruff and mypy

[allenporter]

Thank you for the offline iteration, the new paths look great. Thank you @tubededentifrice for adding these new capabilities!