Simple data-not-found handling and local storage cleanup
This is a simpler solution for !92 (closed). i.e.
- we clean up when we get a
DATA_NOT_FOUND
error, or - we clean up once, after the first time we see a
verify-no-match
The advantage is that it is simple, plus we only ever run list
once for this purpose.
In the future, we might want to add a feature flag to libfprint so that we don't need to unconditionally check after verify-no-match
. But, as of now, all drivers that provide STORAGE_LIST
also need the check.