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/platforms/stm32f7/examples/support/mod.rs

@@ -0,0 +1,11 @@
+//! UART catalog for compile-check examples.
+use platform_stm32f7::{
+    F722UserConfig, UART1, UART2,
+    kaptan_ports::{PortCatalog, PortDescriptor},
+};
+pub struct Both;
+impl PortCatalog<2> for Both {
+    const DESCRIPTORS: [PortDescriptor; 2] = [UART1, UART2];
+}
+pub type UserConfig = F722UserConfig<Both, 2>;
+pub const FACTORY: UserConfig = UserConfig::FACTORY;