Lazy (H)AMT value decoding

[Stebalien]

Currently, our rust HAMT and AMT implementations eagerly decode. Unfortunately:

1. This means we need to eagerly decode everything (and re-encode on save).
2. This causes what appears to be a significant amount of code bloat as HAMT and AMT internals now need to be monomorphized on a per-value-type basis. If we instead decoded into some form of "deferred" object (as we currently do in go), the core HAMT & AMT code could be value (and even key) agnostic.

[raulk]

@Stebalien P3 + Phase 1 basically means it's not going to happen. We are moving this to Phase 2 and can bump the priority. Please shout if you wanna oppose!

[Stebalien]

This is not an immediate priority.

[Stebalien]

This likely isn't worth it. We've actually had the opposite issue in the Go libraries because lazy-decoding means we have to walk the cbor twice and copy everything twice.