Warn against contentEditable with children props

Implemented invariant to guard against #1466 

**EDIT:** Hmm, an argument against keeping `dangerouslySetInnerHTML` out of the validation would be that there are situations in which you might want, and it is practically feasible, to two-way bind a contentEditable (imagine; a regular text-field but slightly more flexible).