Assignments should strip off any ConfigNode wrappers. about configurator

[wimglenn]

Nested containers remain an ConfigNode instances after mutation, reproducer:

>>> cfg = Config({"a": {"k1": [], "k2": {}}})
>>> cfg.a = dict(sorted(cfg.a.items(), reverse=True))
>>> cfg.data
{'a': {'k2': configurator.node.ConfigNode({}), 'k1': configurator.node.ConfigNode([])}}

[cjw296]

Yeah, I feel like this is a tough one. Like we talked about: configurator should arguably strip off the ConfigNode wrapper at assignment time, but there will likely be cases where this doesn't work (assigning a dict mapping to ConfigNodes, etc).

I feel like the answer might want to be "you should be using the mapping/merging APIs" but want to leave this open for the next time I have a proper chance to play with this project...