Upgrade to large capacity SMT

[Mirko-von-Leipzig]

This is currently under construction and would first have to be integrated into base.

This should replace the current account and nullifier trees which are currently stored in-memory.

[PhilippGackstatter]

Should we open an issue in miden-base to change AccountTree to be based on LargeSmt (once we have upgraded to the appropriate miden-crypto version)? I imagine we'd want to change it to something like:

struct AccountTree<STORAGE: SmtStorage = MemoryStorage> {
    smt: LargeSmt<STORAGE>,
}

[bobbinth]

Yes, we should have an issue for this in miden-base - though, I wonder if there is a way to make AccountTree generic over the backend in such a way where we could use either just Smt or LargeSmt. But maybe that's too much work for relatively little gain.

[drahnr]

Yes, we should have an issue for this in miden-base - though, I wonder if there is a way to make AccountTree generic over the backend in such a way where we could use either just Smt or LargeSmt. But maybe that's too much work for relatively little gain.

As part of the work in #1229 I'll be touching this code in particular already. It might be advantagous to let that land before refactoring AccountTree, since it appears I might have to do that already as part of it.
At this time I am not certain how I want the AccountTree just yet. It might be that it's going to be a wrapper around HistoricalViews layered on-top of an Smt, or a deep integration of both.

[bobbinth]

@drahnr - this can be closed, right?

[drahnr]

Done