Mission was not started when regaining connection to ISAR

[andchiind]

Describe the bug
The robot went online but the return home mission in the queue did not start.

To Reproduce
Turn off ISAR when it is running a mission, then restart it. The return home mission does not start.

Expected behavior
The mission should start when the robot becomes available, but the logs indicate that the robot was believed to be not connected. We may need to avoid re-reading the robot state in an event handler, as this can cause such an inconsistent state. If an event is recieved that the robot is reconnected, then we should not read in the robot state again in such a way that this value can be overwritten. This is one potential cause for the bug,

Screenshots