[data.search] Do not send keep_alive after a session is sent to background

[lukasolson]

Summary

After a search session is sent to background, we no longer want to send the keep_alive parameter in our subsequent polling requests, because doing so will override the keep_alive we set when sending to background. This PR updates the search strategy behavior with this change.

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

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

[lizozom]

This looks good, but I wonder if we can somehow test for the race condition where the save that increases the keepalive happens, but then a search polling request that was triggered before the save comes in without isStored and reduces the keepalive irreversibly.

[lukasolson]

@elasticmachine merge upstream

[lukasolson]

We also need to think about the case where the search completes & the user stays on screen for awhile before sending to background.

[kibanamachine]

💚 Build Succeeded

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

Metrics [docs]

Distributable file count

id	before	after	diff
default	47241	48001	+760

History

• 💚 Build #92930 succeeded 1781a44

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