Allow File Data Sources to update an entity

Currently, different File Data Sources can create multiple entities with the same ID.

File Data Sources should instead be able to update an entity with the same ID. Note that this will not be an upsert, which is the current pattern that is used for chain-based data sources. Instead this should completely overwrite the prior entity.

Situation:

file data source A created in block 1
A is found, saves entity X
file data source B created in block 5
file data source C created in block 10
C is found, saves entity X again <-- this is the most recent
B is found, saves entity X again

Entity updates should apply a "most recent wins" approach, where the time is determined by block time, not handler execution time. This is a new pattern (where entities might be created with closed block ranges), and order will need to be resolved within blocks (as well as between blocks)

Non viene indicato alcun file, test o punto di ingresso. Inizia tracciando il modo in cui le origini dati dei file salvano le entità e confronta quel percorso con il pattern di upsert basato su chain esistente, quindi determina come vengono rappresentati il tempo del blocco e l'ordine all'interno di un blocco. Il lavoro è completato quando i salvataggi ripetuti usano il valore più recente ordinato per blocco e sovrascrivono completamente l'entità precedente senza eseguire un upsert.