Status objects threads

Ophyd Status objects (StatusBase, Status, DeviceStatus, AndStatus, etc.) start threads "in the wild" in order to execute callbacks associated to the status change event ("finished" or "exception") ; threads are required because the callbacks are not only triggered when the status is changed programmatically, but also automatically after a timeout+settle time (which can then be an error status).

However, in all ophyd devices code, the behaviour with the timeout is not desired. It is even worse, because it creates threads for nothing.

So, a possible solution could be to patch ophyd in order to prevent the creation of those threads.