Consider erasing data in proposed mempool nodes #1253
Description
The ProposedBatchNode and BlockNode don't perform any aggregation - that is, they don't erase internal notes, nor aggregate account updates. They only delegate the state their transactions/batches create.
This means that a proposed batch and proven batch differ in the state they emit since the latter erases internal-only state. This has no material impact; but does this can be unexpected since it means a proposed batch can be dependent on itself (which we account for in the children/parent functions).
We can avoid this by performing the aggregation ourselves.