Add fingerprint to DB before calling clients

Some clients may call getEnrolledFingerprints when they receive
onEnrollResult.  If the settings database is not updated before
that call there will be a mismatch between the fingerprints stored
natively, and those in the settings database, and when merging the two
lists the new fingerprint will end up being removed from the native
storage.

Change-Id: Ic45423f73939213b85c727cd6cbb048231605b47