Fix memory leak by removing use of WeakMap

* Refactor localization to not use WeakMap as WeakMap seems to Cause a memory leak.  New mechanism avoids weakmap in favor of a reference to the parent object, which is safe because it one-way.  child->parent.

* Adjust get_localized_data to be attached to localize_info hidden element.

Signed-off-by: Jay Kuri <jayk@ionzero.com>
prepare for release.  Bump to 1.1.0

Signed-off-by: Jay Kuri <jayk@ionzero.com>