use latest mavlink definitions for MAV_ODID_ARM_STATUS

[BluemarkInnovations]

• MAV_ODID_GOOD_TO_ARM message have changed in the official mavlink repository some time ago in this PR MAV_ODID_ARM_STATUS entries update to naming convention mavlink/mavlink#1883
• this was also raised in this ArduRemoteID issue Update enum values for MAV_ODID_ARM_STATUS to match the main MAVLink repository ArduRemoteID#35
• other PRs will be submitted for ArduRemoteID and ArduPilot to allow the move to the new ENUMs.

[hendjoshsr71]

This is correct to do but we need to merge at the similar time the associated (nonexistent?) AP PR after this goes in to fix the names and move forward the mavlink submodule

AKA the mavlink double shuffle.

[BluemarkInnovations]

This is correct to do but we need to merge at the similar time the associated (nonexistent?) AP PR after this goes in to fix the names and move forward the mavlink submodule

AKA the mavlink double shuffle.

You are right, I forgot to submit a AP PR, as I initially thought this message was not used by AP.

AP PR: ArduPilot/ardupilot#22460

In general also the OpenDrone ID of Mission Planner need to be updated. I'm in the progress of setting up a build environment for that, but it is a bit time consuming.