BatchBuilder followups

After https://github.com/0xMiden/miden-client/pull/2177, there are some things still worth looking into:

- Recover from failed tx without discarting whole batch. https://github.com/0xMiden/miden-client/pull/2177#discussion_r3275244155
- For this we need to analize wheter or not we can defer updating the in memory data store until we fully know that a transaction is succesfull.
- Remove `get_account_interface`. It currently fetches the full account to get its interface, which is sub-optimal https://github.com/0xMiden/miden-client/pull/2177#discussion_r3285317043
- Decouple `Client` from `BatchBuilder`. https://github.com/0xMiden/miden-client/pull/2177#discussion_r3285329829
- Make BatchBuilder generate a single store transaction update. https://github.com/0xMiden/miden-client/pull/2177#discussion_r3285337241
- Remove producer before consumer restriction for transaction order. https://github.com/0xMiden/miden-client/pull/2177#discussion_r3285352242
- Reduce in memory batch data store size by only keeping `PartialAccount`s. https://github.com/0xMiden/miden-client/pull/2177#discussion_r3285359506

Rivedi la PR #2177 e le discussioni collegate per comprendere le modifiche a BatchBuilder. Esamina l'accoppiamento tra client e batch builder nel codice, probabilmente in src/client.rs e src/batch_builder.rs. L'obiettivo è implementare i follow-up elencati, come il disaccoppiamento dei componenti e l'ottimizzazione della memorizzazione dei dati. Il successo significa che ogni voce viene affrontata senza interrompere la funzionalità batch esistente.

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