[Search Sessions] omit searchSessionId from the initialState, explicitly pause refreshInterval in restoreState

[Dosant]

Summary

Closes #88567 #88568

This pr closes two-issue around restoring a search session in Discover and Dashboard:

1. searchSessionId should be omitted in initialState

We save two states into a search session saved object:

• restoreState
• initialState
  These states are used when navigating from management to an App. By default restoreState is used to restore a session.
  We use initialState when we know there is no session to restore, for example, in case the search session is in the ERROR or EXPIRED state. initialState should not contain searchSessionId, otherwise search requests will error out.

How to test

When saving a session there should be no searchSessionId inside initialState in a request save request payload.

To test end-to-end needs #81707. In case the search is is in the ERROR or EXPIRED state, navigating to it should just restart a search.

2. refresh interval should be explicitly paused when generating restoreState for dashboard.

If there is no refreshInterval in the URL dashboard picks up whatever is saved in the dashboard SO.

[elasticmachine]

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

[kertal]

Kibana App owned code LGTM, tested locally in Chrome, searchSession at intialState is successfully omitted in Discover 👍

[ThomThomson]

Presentation team changes LGTM. Code only review, but will look into testing the full set of features with #81707.

[Dosant]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 492e983

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
dashboard	200.3KB	200.4KB	+156.0B
discover	511.3KB	511.3KB	+82.0B
total			+238.0B

History

• 💚 Build #99962 succeeded 629f112
• 💚 Build #99925 succeeded ae4209b
• 💚 Build #99516 succeeded f227d2b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream