Add start_capture vfunc to FpImageDevice
With the new "idle" state there is a distinction between "activating" a device (e.g. running calibration) and starting a capture operation. We should make this explicit by adding the appropriate
start_capture vfunc with a parameter whether we are waiting for a finger first.
Doing this should allow removing the
change_state callbacks from most/all image drivers.