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-config-derive/tests/ui/numeric_rules_on_bool.rs

@@ -0,0 +1,24 @@
+use kaptan_config_derive::Config;
+
+#[derive(Config)]
+struct NonzeroBool {
+    #[config(id = 1, key = "value", unit = "")]
+    #[config(nonzero)]
+    value: bool,
+}
+
+#[derive(Config)]
+struct RangedBool {
+    #[config(id = 1, key = "value", unit = "")]
+    #[config(range(min = 0, max = 1))]
+    value: bool,
+}
+
+#[derive(Config)]
+struct FiniteBool {
+    #[config(id = 1, key = "value", unit = "")]
+    #[config(finite)]
+    value: bool,
+}
+
+fn main() {}