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/kaptan.xml

@@ -1,7 +1,6 @@
 <?xml version="1.0"?>
 <mavlink>
-  <!-- The root is the only bindgen input. Every current message has one leaf
-       under its interaction contract. exchange/ intentionally has no message. -->
+  <!-- The root is the only generator input. Each message has one private leaf. -->
   <include>publish/log.xml</include>
   <include>publish/error.xml</include>
   <include>publish/heartbeat.xml</include>
@@ -10,4 +9,5 @@
   <include>publish/optical_flow.xml</include>
   <include>transfer/file_control.xml</include>
   <include>transfer/file_data.xml</include>
+  <messages/>
 </mavlink>