Check List

• Tests has been run in packages where changes made if available
• Linter has been run for changed code
• Tests for the changes have been added if not covered yet
• Docs have been added / updated if required

Broken off from #2196

I ran into some issues while making other changes to the React QueryBuilder, and realized that it was because the QueryBuilder was neither fully controller nor uncontrolled, and was using the React anti-pattern of unconditionally copying props to state. Following the recommendations in that article and based on my experience as a React developer, I decided to make QueryBuilder uncontrolled. This means that QueryBuilder controls it's own state, and can't be modified from the outside save for in specific ways that are allowed through props.

This involved deprecating the query, setQuery, vizState, and setVizState props, and adding the initialVizState and onVizStateChanged props. From my analysis, the most common use case for accessing the vizState outside of the query editor is to save the editor state in persistent storage. These two new props allow for setting up a QueryBuilder component from a saved state and then listening for changes to save back. I'm using this in my app to save the vizState to a database so I can persist the QueryBuilder state across reloads.

I also added the defaultQuery and defaultChartType props, so that if initialVizState is empty, it will pick up the default values for those. defaultChartType was listed in the documentation before, but wasn't actually implemented until now.