[State Management] Inconsistent behavior with saved queries

[sulemanof]

Kibana version: latest

Elasticsearch version: latest

Describe the bug:
The behavior in the legacy apps like Discover, Visualize and Dashboard using the savedQuery doesn't look obvious.
To understand, what is going on, you have two create couple of saved queries:

• Create two different saved queries with at least one filter in each, e.x.:

  

General steps:

a) Create a new instance of Visalization/Dashboard/Discover

b) Add any of created savedQuery to the search:

c) Add additional filter to the search, e.x.:

There are several possible cases described below 👇

Reloading the page

Make all of the general steps. Reload the browser window.
Custom app filter will gone, the saved query filters take precedence over app filters.

Addressed in #59805

Changing the savedQuery id in the url

Make all of the general steps.
Change the savedQuery id in the url, e.x. savedQuery:spalger -> savedQuery:member, press enter.
Saved query is changed, custom app filter will gone, the saved query filters take precedence over app filters.

Addressed in #59805

Save the Visalization/Dashboard/Discover

Make all of the general steps. Save your created instance with the Save button.
All of the filter will become appFilters, the savedQuery is not selected anymore.

Opened separate issue #59808
Also, visualize and discover should switch to use use-default-behaviors for consistency.
#59811
#59812

Proposal

My proposal is to the behave in one way.
The saved query filters should be merged with the app filters, but not be removed at all.
The saved query will still take a precedence (means overlapping filters will go to saved query),
but the app filters will be not lost.

[flash1293]

@timroes Do you know of any previous discussions about the behavior of saved queries that could be referenced here?

[timroes]

I wouldn't know what to link to for this right now. Since filters and the saved queries are now maintained by app arch I'd ping @alexh97 here for awareness, and also @AlonaNadler since she might know about prior discussions around how the behavior should be.

[kertal]

added @lizozom because of #56160 (Stateful search bar default behaviors), it currently only used in discover but that will change

[elasticmachine]

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

[lizozom]

Like @kertal had mentioned, the inconsistency is a result of the fact that discover uses use-default-behaviors while visualize and dashboard still implement their own version.

I will work on fixing those issues when using use-default-behaviors, and once visualize and dashboard start using it, we should be good

[lizozom]

Broke down this issue into individual tasks