[Search Sessions] Restore state from SO instead of URL

[Dosant]

Part of #83640

Problem

Initial version of search session restores state from the URL.

The URL contains both serialized app + searchSessionId:

kibana/app/discover/#/?_a={discover_state}&_g={discover_state}&searchSessionId={id}

If state in the URL changes and searchSessionId stays untouched most likely session restoration would fail because search requests during restoration wouldn't match original search requests saved within the session:

• User manually changes URL
• Something else changes the URL and leaves searchSesssionId. e.g. [Search][Send to background] Restoration URL conflicts with global time sync with chrome's URLs #87149

Solution

By searchSessionId we can restore the application state from search session SO.

Instead of relying on rest of the app state when searchSessionId is present in the URL we could try to get the state stored in SO, so searchSessionId becomes single state source of truth.

Related

• [Search Session] Use new URL Service for session restoration #85126
• [Search][State Management] Restoring background session and back button #82419

[elasticmachine]

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