RN-1162: Fix visibility criteria check not updating when a answer changes

[rohan-bes]

Issue RN-1162:

Pretty simple bug. We assumed that the data coming through onChange as a change event. Reworked it so that we now should always return the actual new data when an input changes. This feels like the right approach, though I'm not sure if there's anything that we're mis-using/loosing from react-hook-form here...

[alexd-bes]

I think this is a good approach - the tricky part of this is the different inputs that might come from ui-components and what they return in theonChange event. I have left a comment about autocomplete questions, but other than that, pre-approving

[alexd-bes]

So there is a slightly weird case here, I think it's possibly in the autocomplete question and maybe also the entity question, where the onChange event returns an object with value as opposed to a typical change event object, so we would need to handle that case as well

[rohan-bes]

@alexd-bes thanks for noting this, my original approach wasn't working with autocomplete questions as you predicted.

I decided to go with a slightly different approach this time. Now onChange takes two arguments, the first is the input value and the second is the raw value. That way we can let react-form-hook still do it's thing while also passing in the raw value to updateFormData()