removing dinitialize

@mattpap @bryevdv @tabchas  I think when I started I didn't know javascript and backbone well enough to do this, but I think this is sufficient to get rid of dinitialize.  Essentially we rip out backbone.js constructor, make the initialization call optional, and when we would like to defer it (loading a bunch of models) then we pass in an option to skip the initialization because the code that loads a bunch of models goes in afterwards and makes all the initialize calls.

It seems to work in a simple test case (the log scale one). I would not merge this in for this release (no benefit to the users really)  But this should make our future development smoother.

@bryevdv I don't think this would have made your layout development any easier, all the things we talked about with regards to simplifying and documenting and understanding the events we use is still important going forward, I think that is what will make some of the complex work we have coming up easier to do