Abstract: We want to add a feature/fallback for when we want to manually intervene in a mission and alter the mission state.
This is motivated by the need to rollback states during mission in competition, and is generally a good feature when considering that we may be forced to manually land to troubleshoot. In such case, the ability to rollback the mission state while retaining specific configurations + images would be ideal.

Considerations:

• This feature does NOT mean we should allow ANY tick to be set by the GCS operator. We need to consider specific states such as WaitForTakeoff, or FlyWaypoints which are comparably easier to revert back to considering the need to revert mission_state elements as well. This will require some brainstorming with leads about what backtracking states should be allowed and what state elements need to be reverted/altered while others are kept. (Ex. How do we revert # of laps flown, or what airdrops have been dropped?)
• We should consider parallel elements like the camera or server and how they may need to be reverted depending on the movement of states.
• Also consider the UX on the GCS side, as we should choose how the tick is rolled back carefully to avoid any illegal/dangerous state modification.