Cache Hydrated Conversations

[jazzz]

Problem

Currently the approach to managing conversation state is based on hydrating conversations from storage on every call. This has negative impacts on performance, readability, and ownership.

Whats needed

• Clients or Inboxes should cache Conversations it has already loaded into memory.
• Conversations state is persisted as needed.

[jazzz]

Block on updates to the ServicesContext