Maintain sorted operation indexes

[sandreae]

We want to persist and maintain sorted position indexes for all operations which have been materialized into a document. This index is the operations position once topological sorting has occurred and can be understood as the sorted_index of a particular operation, or also the documents "depth" at that point in it's history.

This is done by introducing the following:

• add a sorted_index column to the operations_v1 table
• update all operation models and data types accordingly
• introduce a update_operation_index method to the OperationStore
• in a reduce task update the sorted_index of all operations in a document

Note, there is a period of time when an operation has been inserted into the store, but it's sorted_index is None because materialization has not been performed yet. As we have a "retry" system already in-place to account for a node shutting down unexpectedly before tasks could be completed, then we can be confident all operations will be processed and have their sorted_index set eventually.

📋 Checklist

• Add tests that cover your changes
• Add this PR to the Unreleased section in CHANGELOG.md
• Link this PR to any issues it closes
• New files contain a SPDX license header

[codecov]

Codecov Report

Patch coverage: 93.75% and project coverage change: +0.13 🎉

Comparison is base (ae27ff2) 90.05% compared to head (57813bd) 90.19%.

❗ Current head 57813bd differs from pull request most recent head 2d93eb5. Consider uploading reports for the commit 2d93eb5 to get more accurate results

Additional details and impacted files

@@               Coverage Diff               @@
##           development     #438      +/-   ##
===============================================
+ Coverage        90.05%   90.19%   +0.13%     
===============================================
  Files               87       87              
  Lines             8439     8514      +75     
===============================================
+ Hits              7600     7679      +79     
+ Misses             839      835       -4     

Impacted Files	Coverage Δ
aquadoggo/src/db/types/operation.rs	86.66% <ø> (ø)
aquadoggo/src/db/stores/operation.rs	89.01% <90.76%> (+4.54%)	⬆️
aquadoggo/src/materializer/tasks/reduce.rs	90.07% <95.91%> (+1.28%)	⬆️
aquadoggo/src/db/models/utils.rs	99.46% <100.00%> (+0.01%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[adzialocha]

Great!!

Note, there is a period of time when an operation has been inserted into the store, but it's sorted_index is None because materialization has not been performed yet. As we have a "retry" system already in-place to account for a node shutting down unexpectedly before tasks could be completed, then we can be confident all operations will be processed and have their sorted_index set eventually.

That's half working actually, but with this PR we have everything in place I think to help us with it: #441