feat(firmware): validate configuration and migrate sensor-driven flight APIs

Validate configuration through its owning schemas and keep board
declarations separate from shared F722 resource ownership. Bound USB
transitions, isolate transport failures and retain restart-only activation.

Migrate navigation and flight consumers with the sensor and schema
contracts. Require explicit installation data and synchronous output
authority; board motor outputs remain inhibited.

Validation: assembled-prefix host tests, strict Clippy, platform/USB tests
and both ARM release builds. Final-source coverage and scoped Miri/Kani
evidence are retained separately from hardware qualification.

firmware/libs/kaptan-mavlink/definitions/publish/log.xml

@@ -21,7 +21,7 @@
   </enums>
   <messages>
     <message id="51020" name="LOG">
-      <description>Bounded human-readable runtime log emitted by every Kaptan logging macro, including error. The receiver needs only level, flags, and the valid UTF-8 text prefix. MAVLink framing, bounded admission, DMA, and retries remain platform-owned.</description>
+      <description>Runtime log emitted by Kaptan logging macros, including error.</description>
       <field type="uint8_t" name="level" enum="LOG_LEVEL">Kaptan wire level.</field>
       <field type="uint8_t" name="flags" enum="LOG_FLAGS">TRUNCATED=1. Receivers ignore unrecognized bits.</field>
       <field type="uint8_t" name="message_length">Number of valid UTF-8 bytes in message; at most 160.</field>