fix: aggregator idempotency

restart from the beginning of conclusion events to avoid skipping on restarts. need to figure out why memory table contains conclusion_event_order that is less than the data written to event_states still, and hopefully restart where we left off. for now, we just ignore things we've seen before.

Author: dav1do

Cargo.lock

@@ -52,3 +52,5 @@ url.workspace = true
 mockall.workspace = true
 test-log.workspace = true
 tracing-subscriber.workspace = true
+rand.workspace = true
+multihash-codetable.workspace = true