Mock driver experiment

Okay I know what I did here. I had another 'check_status' function in the MockRemoteConnection class, so that it would short circuit the parent RemoteConnection status. 
This was mainly because as I handled the recording in the beginning, I recorded only a session, and not every possible session, so I was not able to catch the 'status' call. 
Right now, everything is recorded just fine, so we can remove the MockRemoteConnection 'status' call, but we have to update the recordings, so the status calls are recorded. 

As for the code, I think we need to go deeper : check_status as it is should not exist, as it short-circuit the Driver logic. What I would see is that we use '_execute_command' in the Driver to perform the status call, and then parse the response and croak accordingly. 

You might want to address this in a separate issue, what do you think ?