Add safeguards for when async storage retrieval fails

[achou11]

Have only run into this during development but I think it highlights an eventual issue that we'd ideally avoid when it's deployed

Not sure about precise reproduction steps, but basically when opening the app, it sometimes gets stuck on the splash screen. I have to uninstall the app entirely or clear the app storage and restart the app in order to fix it. The annoying this is that there's no clear error that gets surfaced when this happens.

My suspicion is that there's something with the zustand persistence + mmkv where we run into this situation, mostly in development because of the frequent refreshes (via react fast refresh) or git branch switching. Think this mostly highlights the need to have the proper error handling in place in case this does happen in the wild (which it very much can)

Might require some design work in terms of figuring out what kind of error we should show (or if we should do something more aggressive?)