[data] query state as a single source of truth used by components that handles automatic and user interactions

[kavilla]

Is your feature request related to a problem? Please describe.

With new components that have the ability to update the query state from user interactions and automatically, it is very easy for the application to get in a weird state through some unexpected interaction from when the original feature was added.

Describe the solution you'd like

There should only be one source of truth for query state and it should match the app query state. Firing the query should be restricted to when the user is ready, but should not prevent the app query from changing.

The query string manager should be able to distinguish or we use UI actions properly to determine if it's a user interaction or not.

Describe alternatives you've considered

n/a

Additional context

n/a