device: Fix race when client vanishes from bus
We have a condition where a client vanishing instead of cleaning up the operation using VerifyStop would cause fprintd to hang. This only happens if the underlying enroll/verify/identify operation has already finished when the client vanishes.
Fix this by correctly interpreting current_cancellable as a flag for these operations.
Fixes: #97 (closed)