Collapse Update Jobs when receiving multiple blocks

[Sword-Smith]

When a block comes in, (and assuming the right CLI flags are set) a task is spawned to handle all the proof updates (from SingleProof to SingleProof with updated mutator set commitments). However, this list of update jobs could very well refer to multiple instances of the same transaction. We should ensure that if we apply blocks e.g. 4 and 5, that a transaction is updated directly from the previous to the new tip (from 3 to 5) and not updated to intermediate blocks (i.e., updated from 3 to 4 to 5 in two separate proofs).