March forward with progress breaking things...

... Yesterday's reform of the AddressTokenBinder class seems to be working pretty well. I've bug into some lingering concerns w/ONMjs.Namespace and further reduced the amount of context it maintains. Specifically ONMjs.Namespace no longer caches an array of AddressTokenBinders. Instead, I now simply maintain the current data namespace reference into the store, and create the resolved token array inline with the resolution of the incoming address token array (note that the incoming address token array is traversed to create a sequence of AddressTokenBinder instances. it's just now we extract what we need from the AddressTokenBinder and throw it away as opposed to keeping them around in their own array. This has downstream ramifications on observers as I've ripped out helper methods for accessing token binders that we no longer cache. It seems that all that's really typically sought is the last resolved token anyway so it's just a matter of tracking the bugs down and reworking the offending observer code that relies on binders when all they really need is the data ref and resolved token.

Also, this commit has component create signals offline.