[Bug] MAVLink multi-instance mission state conflicts.

[hanhui03]

Describe the bug

The MavlinkMissionManager::MavlinkMissionManager class during construction, only one instance will read the mission status and update private members such as _land_start_marker and _land_marker. For other instances, these members are initialized to -1. If another instance sets a new seq via MAVLINK_MSG_ID_MISSION_SET_CURRENT, the wrong _land_start_marker and _land_marker will be written to dataman and publish a wrong mission state.

To Reproduce

No response

Expected behavior

No response

Screenshot / Media

No response

Flight Log

No response

Software Version

No response

Flight controller

No response

Vehicle type

None

How are the different components wired up (including port information)

No response

Additional context

No response

[github-actions]

This issue has been marked as stale due to 90 days of inactivity. If no further activity occurs, it will be automatically closed in 30 days. Please leave a comment, add a reaction, make an update, or remove the stale label if you’d like to keep it open.

[github-actions]

This issue has been automatically closed due to 120 days of inactivity. If you believe this is still relevant, please feel free to reopen it or create a new issue.