[bug] create and update form API does not validate passed values against enumerated options

[signebedi]

When we have passed an enumerated set of options that a form field may adopt, user data should be validated against these to ensure that assumptions are not broken regarding the structure of the data. For example, what if a user submits data using the API that does not conform to the set of available options for a checkbox field, and then another user goes to modify that using the front end. Key assumptions here will be broken that will ultimately harm the user experience.

[signebedi]

The key idea here is that the options passed as part of a field in the form config is not currently used as part of the RESTful API to assess data; it is only used to generate a list of options for the UI. This is problematic for data that is submitted through the API but sometimes accessed and edited within the UI - especially data containing radio, checkbox, and select fields where the value passed during initial creation in the RESTful API isn't among the list of enumerated options... So there will be some broken logic.