Update to make the view be the domNode instead of having a view.domNode....

... I added a viewFactory to create the view and return the view domNode since that seemed to make sense. There were also a couple of view variable names which had to change to avoid conflicts with the domNode, parentNode became viewParentNode, and children became childViews, destroy became beforeDestroy.  Most tests were updated to remove .domNode when setting things on the view and make updates for the variable name changes.
Right, I do need it on the view (not the domNode) in ViewBase before the domNode is added to the parentNode, but I guess I could just add code to skip mixing it into the domNode, and then I could leave it as parentNode and it should be ok.