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

@@ -5,7 +5,7 @@
   <messages>
     <message id="51029" name="RANGE">
       <description>One accepted downward range observation from the board's selected vertical sensor route.</description>
-      <field type="uint64_t" name="time_us">Flight-controller monotonic measurement-request time in microseconds.</field>
+      <field type="uint64_t" name="time_us">Producer timestamp in flight-controller monotonic microseconds: measurement request for LIDAR-Lite, frame reception for MTF-01.</field>
       <field type="uint32_t" name="distance_millimetres">Measured downward distance in millimetres.</field>
     </message>
   </messages>