Fingerprint Wakeup: add some error handling; fix race conditions

- If the FingerprintManager reports that the HW is unavailable, it's
likely the service isn't up yet. Try to reinitialize the fingerprint
state when this happens.

- Fix a race condition when screen is turned off and fingerprint is
recognized but keyguard has not yet come back up.

- don't count Fingerprint sensor errors against failed user count

- Always stop authenticating when keyguard goes away.

- Make final vibrate when limit has been reached more obvious

Fingerprint Service changes:
- Don't remove wake client when removing listener. These should be
  handled separately.

- Remove wake client when wake is disabled

- remove finalize() call - the binderDied() interface accomplishes what
  we need to do the proper cleanup.

Ref: CYNGNOS-1125

Change-Id: Id22d8f4f409e3989d0a094eb4c4bab7da996937f
Signed-off-by: Roman Birg <roman@cyngn.com>
(cherry picked from commit 17775a65)