Building up new navigator based on store observer notifications...

... and leveraging observer private namespace storage to dramatically reduce the size and complexity of a model view observer. The goal is to import some of the chrome from the old navigator, and then completely remove the old navigator. Gone are the days when the presentation layer has any direct say in the contents of the underlying data model. Now the data model is declared as an Object Model declaration (Javascript object), used to instantiate an ObjectStore, and then an instance of ObjectStore. Clients may create and remove components, open existing store namespaces by selector, and broadcast manual updates to model view observers registered with the store instance. In this commit the refactored navigatar implements onNamespaceCreated and onNamespaceRemoved callbacks and leverages observer private store obtained from the object store to maintain internal data required by the Knockout.js MVVM presentation layer. The concept of navigator selection is actually now orthogonal to the data model as it should have been all along.