Robot's movement threads are not closed on KeyboardInterrupt

[Fabulani]

If the Scenario is in a state where a Robot is moving around (a movement thread is open and running), and the user does a KeyboardInterrupt, the main thread will shut down, but the Terminal will be stuck with the movement threads.

A solution would be to add daemon=True to any created threads, but a more long-term solution is to improve the current parallel movement implementation.