Quickly ran into problems with param based approach here when tried to work on a second one.
setState is an async function. But, in react, there is not a practical way to await this. You can reliably trigger actions to happen when state changes, e.g. a callback or useEffect. However this would make for a long daisy chain of loading functions to get everything we need into cashtabState.
Because we always want to load all of the localforage stuff at the same time on startup, we do not need to use a key...value approach and various customizations depending on the key. Instead, go through and load/validate/migrate everything.
Note: for now, we still have only implemented contactList in the new cashtabState general object.