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)

No se nombra ningún archivo, prueba ni punto de entrada. Empieza por rastrear cómo las fuentes de datos de archivos guardan las entidades y compara ese flujo con el patrón de upsert basado en cadenas existente; después, determina cómo se representan el tiempo del bloque y el orden dentro de un bloque. Se considera terminado cuando los guardados repetidos utilizan el valor más reciente ordenado por bloque y sobrescriben por completo la entidad anterior sin hacer upsert.