Make return-to-home more robust

[Eddasol]

Describe the improvement you would like to see
Return-to-home have several issues:

• If arm is moved the robot will try to schedule a return-to-home mission. The mission will fail and do nothing as the robot is missing current area, but the scheduling attempt shouldn't happen at all. Move robot arm triggers Return to Home Mission #1466
• If robot is turned off without being allowed to complete return-to-home mission it will start a return-to-home when it gets started again. Should there be some timer that de-localizes the robot after a certain time if nothing happens (idle/offline?). Related to We need a more robust way of resetting the current area to null #1450
• Scheduling a new mission while the “Return to home” mission is ongoing #1464

How can we make return-to-home behavior more robust?

In addition, I am adding this to the epic because I believe it is somehow related and would be good to get it all implemented in one go.

• If robot battery is running low, stop the missions and send it home #1459

How will this change existing functionality?

How will this improvement affect the current Threat Model?

[aeshub]

This issue has automatically been marked as stale as there has been no activity for 60 days.

[aeshub]

This issue has automatically been marked as stale as there has been no activity for 60 days.

[andchiind]

Replaced by other issues. This is no longer relevant.