Robot script still running when UrDriver object is destroyed

When the UrDriver object is destroyed and the robot is controlled by the UrDriver the script will continue to run on the robot until the socket connection times out. This socket timeout is configurable meaning that the timeout determines when the script stops executing. I suggest that we as part of the destructor in the UrDriver makes sure to stop the control of the robot. 