[Feature] Deployments with limited history should not keep history during syncing

Description

When syncing a subgraph that has limited history, i.e. has history_blocks set, we should not keep any history while we are syncing more than history_blocks away from the chain head. When storing an update to an entity, simply overwrite the old version of the entity instead of keeping the old and the new version.

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out

• Tick this box if you plan on implementing this feature yourself.
• I have searched the issue tracker to make sure this issue is not a duplicate.

Empieza rastreando la ruta de actualización y almacenamiento de entidades que se utiliza al sincronizar deployments con history_blocks; el issue no especifica archivos ni tests concretos. Confirma cómo se conservan las versiones más allá de la ventana de historial configurada y, después, añade cobertura que demuestre que las actualizaciones más antiguas que la ventana sobrescriben la versión anterior de la entidad, mientras el historial dentro de la ventana sigue disponible.