Fix nasty bug in address token resolver...

... Subtle test break in onm.Namespace.getExtensionPointSubcomponentCount.js actually helped me track down this vexing issue where I was accidentally overwriting the low-level data object in address token resolver instead of working directly with a reference to the established onm.Store data object. Really bad: this caused previously constructed onm.Namespace instances to hold detached data references (i.e. references to data objects no longer held by onm.Store). I want to throw a bunch more test cases at this to ensure it's good before throwing the latest at large onm dependencies (i.e. Azuqua repositories).