Detect erased notes for a network account

Erased notes are not marked as consumed unless they are already present in the store. When the sync detects an erased note (created and consumed in the same batch), it transitions the existing input record to consumed, but if the client never had an input (or output) record for that note, the sync has no way to surface the consumption.

A posible fix would be to add the ability to create input note records from the note header provided by the transaction sync, instead of requiring the full note details. This was initially implemented on https://github.com/0xMiden/miden-client/pull/2090 but discarded to avoid breaking changes for the patch release.

Related: https://github.com/0xMiden/miden-client/issues/1971

Esamina la logica di sincronizzazione per la gestione delle note cancellate, in particolare dove vengono creati i record di input e vengono fatti transitare allo stato consumato. Rivedi la PR scartata #2090 per il contesto sulla creazione di record di note di input dagli header delle note. Comprendi il ciclo di vita delle note e come il consumo viene esposto quando a un client mancano record precedenti.

Scritto dal modello di indicizzazione a partire dal testo della issue.