Start using node-mavlink bindings

[1Blademaster]

No description provided.

[Copilot]

Pull request overview

This PR starts replacing hard-coded MAVLink enums/bitmasks in the GCS with definitions sourced from mavlink-mappings (via a new mavlinkDef helper), as a step toward using node-mavlink-derived bindings across the frontend.

Changes:

• Introduces mavlinkDef helper that aggregates MAVLink dialect mappings and updates several enum/bitmask usages to reference it.
• Refactors mavlinkConstants to derive flight modes, GPS fix types, MAV frames, and EKF status flags from MAVLink definitions instead of hand-maintained tables.
• Updates UI/redux usage sites (dashboard GPS fix display, mission state display, arming/prearm checks) and removes a debug console.log.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
gcs/src/redux/slices/droneInfoSlice.js	Switches arming/prearm checks to MAVLink definitions; updates EKF flag checks (currently inconsistent with returned flag names).
gcs/src/helpers/mavlinkDef.js	New helper that imports and merges MAVLink dialect mappings into a single exported object.
gcs/src/helpers/mavlinkConstants.js	Replaces multiple hand-coded maps with enums derived from mavlinkDef; adds formatting helper for GPS fix labels.
gcs/src/dashboard.jsx	Uses mavlinkDef.GpsFixType[...] directly for GPS fix display instead of GPS_FIX_TYPES.
gcs/src/components/dashboard/tabsSectionTabs/missionTabsSection.jsx	Uses mavlinkDef.MissionState[...] to render mission state.
gcs/package.json	Adds node-mavlink dependency.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.