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

Look at the sync logic for handling erased notes, particularly where input records are created and transitioned to consumed. Review the discarded PR #2090 for context on creating input note records from note headers. Understand the note lifecycle and how consumption is surfaced when a client lacks prior records.

由索引模型根據 Issue 內容生成。