[Maps] use stored map buffer to generate queries for search sessions

[nreese]

Partial fix for #90776

Elasticsearch queries for map layers contain an extent filter to limit results to those around the visible map area. This causes problems with search sessions because if the screen size changes at all, then the extent filter will not match the stored search session query and there will be a cache miss.

This PR solves this problem by storing mapBuffer in the MapEmbeddable input state so that when search sessions are used, the stored mapBuffer can be used instead of the actual map buffer based on the screen size.

This solution is not perfect and there are 2 remaining problems with this approach.

1. Embeddable input state is only persisted when dashboards are saved. This means that MapEmbeddable.input.mapBuffer will not exist for any map embeddable saved prior to 7.12. Users will experience the same error if using search sessions on these dashboards since the fallback will be to use the mapBuffer for the current screen size. This issue can be fixed by having users change the map view to set a new center/zoom/mapBuffer and then save the dashboard. Not a great experience, but better then broken map embeddable when using search sessions and no work around.
2. If the search session is created on a very small screen and the the search session is viewed on a much larger screen, the user's current view port may extend past the cached mapBuffer area resulting in missing data around the edges of the map. The reason being is the query would use the cached map buffer instead of the actually buffer so less area would be queried. In practice, this will not occur often since the mapBuffer is the current view port plus 50% so the screen sizes would have to be very different and the work around is to create the search session on the larger screen.

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[Dosant]

I validated that mapBuffer is now saved into panelsJson and that the maps search session is restored when the search was done with the same state that saved with the dashboard.

[nreese]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: a00d9e8

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
maps	2.6MB	2.6MB	+285.0B

History

• 💔 Build #106827 failed f5dd6e2
• 💛 Build #106254 was flaky ba8a7d5
• 💔 Build #106220 failed 67d7a5c
• 💚 Build #106118 succeeded 4da3e05
• 💔 Build #106094 failed 8dde478

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