Separate architecture for client side cache sharing

[flash1293]

Right now client side caching is piggy-backing on top of sessions. As client side caching needs to be shared across apps in some cases (especially going from dashboard to the visualization editor and back), sessions are shared between apps piggy-backing on embeddable state transfer.

Both of these things have been proven to be sub-optimal, so let's think about how this can be done in a more robust and extensible way.

Requirements:

• It's possible to not lose client side request cache when moving between apps
• It's possible to evict the client side cache in the right places

Reference #115515

[elasticmachine]

Pinging @elastic/kibana-presentation (Team:Presentation)

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServicesSv)

[Dosant]

Also there is currently a bug with session restoration due to client side cache: #106074 (comment)

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[ThomThomson]

Removing the Presentation Team label from this one. Presentation team code is generally data-agnostic, and likely any caching solution would be built on the visualization, data view or core layer.