Statefull <SearchBar/> hardening

[Dosant]

In 7.7 we did a great job simplifying usage of a by adding use-defaults property. It allows to use with all the features (Filters, TimeRange, SavedQueries) with almost non configuration.

But there are use cases when use-defaults has to be used together with regular "controlled" inputs / outputs.
Looks like there are some edge cases could pop-up out in some scenarios causing infinite cycles of state updates. Example: #63505, #63561

I think we should review different combinations of props / state updates to properly fix the issue patched in #63505. Ideally we should also improve unit test coverage of that component and focus on making sure we are not getting into infinite loop with different props/use-defaults combination. We could also look into reducing react recalculations .

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[ppisljar]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.