Alternative storage engine for ParameterStore

[jpmckinney]

fq values can be complex. What are our options?

1. Store the complex values, and write a better parser
2. Delegate responsibility for parameter storage to the widgets

In the second case, widgets can store simple values, which they know how to read to create a complex fq value. Developers should have to "opt-in" to taking this responsibility. Moving this logic out of ParameterStore into each widget means that developers need to think more carefully about which widget is responsible for which parameters/fields. It's not clear what the implementation would look like to preserve flexibility and expressivity.

Google Group discussion

[jpmckinney]

Continued in #13