Implement resumability for revindex

[luizirber]

Allow recovering from a failed create/update by reprocessing signatures that were not marked complete/processed.

Will probably to a version bump in DB (0 -> 1), with V0 assuming all datasets were processed properly, and V1 being able to track which datasets from the manifest failed or where not processed yet.

(From a discussion with @MGS-sails)

[codecov]

Codecov Report

Attention: Patch coverage is 80.48780% with 8 lines in your changes missing coverage. Please review.

Project coverage is 86.67%. Comparing base (8c9dfce) to head (2a3a14f).
Report is 2 commits behind head on latest.

Files	Patch %	Lines
src/core/src/index/revindex/disk_revindex.rs	80.00%	8 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           latest    #3275      +/-   ##
==========================================
+ Coverage   86.66%   86.67%   +0.01%     
==========================================
  Files         137      137              
  Lines       15962    15998      +36     
  Branches     2728     2728              
==========================================
+ Hits        13834    13867      +33     
- Misses       1819     1822       +3     
  Partials      309      309              

Flag	Coverage Δ
hypothesis-py	25.40% <ø> (ø)
python	92.37% <ø> (ø)
rust	62.86% <80.48%> (+0.33%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[luizirber]

@sourmash-bio/devs not sure how to test this one

• we don't have a previous version of the DB as test data, to check if the assumptions hold when updating it (that all sigs in the DB were processed properly)
• how to crash the process in the middle of processing, restart, and make sure it returns same results as if it went all the way to the end?

I did this with https://github.com/sourmash-bio/branchwater and it worked as expected.

Otherwise, ready for review!