Remove UnboundInput #117
Description
There's no reason we couldn't just make boundToForm a flag/prop on <Frig.Input />, which defaults to true.
Going forward anything that reduces the nesting/hierarchy of these components will be a good thing.
Background: <UnboundInput/> was needed so we could create themed components whose inputs didn't directly bind to the form, e.g. TimePickerPopup which has hours/minutes/amPm as separate inputs (so-called "sub inputs") that together represent a single field. There's no technical reason these couldn't just be plain <input> tags, but we took this approach so we could reuse the themed <FriggingBootstrap.Input> tags and keep consistent styling (/prefix/suffix/label/etc) even for unbound inputs.