jobs don't 'complete with error' when start_job fails

[g-kimbell]

When starting a job, if the biologic says it is in state "RUN" the job never starts, and it never switches to 'ce' (completed with error), it stays in a frozen running state and has to be manually cancelled.

The same happens if an error is thrown by drivers.biologic.start_job (e.g. there is a problem with the payload or the firmware isn't loaded), the job stays frozen and running.

[PeterKraus]

I think in general, we need to be more thorough about catching exceptions, logging them, and trying to recover.