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.
I suppose we renamed parentNode to viewParentNode because we get mixed into the domNode that already have a parentNode? But in practice will it be a different node? I mean will the domNode.parentNode not be the View parentNode?