Fix monitoring feedback and alarm events

[mattriney]

Summary

• retain split identity replies and retry only missing fields at a limited rate
• confirm requested accessory power as well as on/off state
• redact device-identifying text from diagnostics exports
• emit an updated controller event when alarm code or axis details arrive later

Testing

• 101 tests passed; 96.80% coverage
• Ruff, formatting, Pyright, HACS, and Hassfest passed
• regression tests cover split replies, mismatched power, diagnostics redaction, and enriched events
• live Z1 Pro on firmware 1.1.2.0.1.13: complete identity returned; spindle fan confirmed 35% and restored off; physical E-stop reported Alarm/code 13, then Idle/no alert after release and Studio unlock

The split-reply and late alarm-detail cases were reproduced in regression tests rather than induced on the live controller.