Handle dehydrating/rehydrating of components (saving state)

[mofojed]

• Client-side
  • Storing what documents we have open, along with the name of the document #160
  • Re-open document on page refresh (don't worry about previous panels at this step) #161
  • Storing which dashboards/layout/panels are open from this document #162
  • Storing state of each element (such as UITable filters that are set) (something like a usePersistentState() hook, from the UITable component) #163
• Render context/Server-side
  • Store the server side render state for rehydration/resuming the element from a state #164

[mattrunyon]

It might be useful to have a PanelContext that contain info about the visibility/state of the panel (hidden, focused, etc.) and that could also be used for providing state. We could add something like a usePersistentState hook and that hook reads from the PanelContext it is in to save to the right spot in redux or something. Not sure how we'd want to go about using that hook (limit to a single call? Require an ID for multiple calls?) but I think it would be useful for functional component state