[BUG][VisBuilder] filter (_q) is not saved which causes un-persistent state

[ananzh]

Describe the bug
There are three types of state in OpenSearch Dashboards visualizations.

• _g : the global state (time range), which is shared across OSD. _g is not saved in saved objects. Once _g is changed, like changing time range, all visualizations, discover, dashboards, & reload a saved object will reflect the updated _g.
• _a: the application state, which represents the application-specific state. This part is saved in saved object. For example, discover _a state is saved in saved search.
• _q: query and filter state, which includes both the query string and the filters applied. In both visualization, except vis builder, and discover, _q is saved in saved object.

For example, in visualization

OpenSearch-Dashboards/src/plugins/visualize/public/application/utils/get_top_nav_config.tsx

Line 110 in 34994f8

savedVis.searchSourceFields = vis.data.searchSource?.getSerializedFields();

For example, in discover, it updates searchSource in saved search via this function:

OpenSearch-Dashboards/src/plugins/discover/public/application/view_components/utils/update_search_source.ts

Line 25 in 34994f8

export const updateSearchSource = async ({

In VisBuilder, searchSource is undefined. _q is not saved. Therefore, _q is not persistent among different saved objects. If you saved filter filter1 and query1 in vis builder, then you load a diff saved visualization (for example a bar chart) with filter 2 and query2, you will observer filter2 and query2 in vis builder. Currently vis builder has an issue of loading query, so you will see filter2. I will open a different issue on missing query. But I think save _q in vis builder will resolve both issue.

To Reproduce

q.persistency.bug.mov

Expected behavior
Expect vis builder to have persistent query and filter _q like other visualization types.

OpenSearch Version
2.10

Dashboards Version
2.10

Plugins

NA