Roll back account states based on mempool errors

We currently roll back account states based on whether transactions went stale (as configured) or if we know they expired (based on whether the transaction expiration was set during execution).

With https://github.com/0xMiden/miden-client/issues/1312, at the moment of submitting new transactions, we can also catch the "account initial commitment mismatch" error and roll back the account states to the correct state commitment because we'd know the mempool has dropped a subset of the transactions that the client sent. For this though, we'd need to get structured error information rather than just an error code (ie, we'd need to extract the account state commitment from the error itself)