feat(organizations): Cache organizations to support offline first UX

[gatzjames]

Highlights:

• Caches the results of fetching organizations and user data to allow the app to keep working while offline
• The data are cached in localStorage instead of in-memory using the accountId as a cache key

Next steps:

• Evaluate better caching strategies and ttl set from the server
• Features and Rules for organisations are a bottleneck for performance atm when switching between organisations and could use a better solution
• Move all localStorage to a file accessible from main context, to avoid localStorage corruption caused by app crashes.
• Rather than using the localStorage to get data in other loaders, we could first render from the cache with a defer to fetch, or an alternative initial load strategy

notes

• we cache org, user, plan at app-start, and sync triggered by SSE
• we read from the cache in three places
• cache mechanism is different to projects because projects are a intersection of remote and local and orgs, user, and plan is just a copy of whatever it the latest state on the remote.
• could cache feature rules responses, but would mean first visits would always have delays, could prefetch or could add to org response?