Incorrect state on nested HardDependencyNode if the child is created before the parent

[Samuel-amap]

In cases where a HardDependencyNode's parent is also a HardDependencyNode, and the child is created before the parent, when the actual node is instantiated, it uses the incomplete parent state (which will not have had its parent and children properly set), leaving the instantiated node in an incorrect state that is not subsequently corrected once the parent is created.

This isn't currently a major issue, as it is easy to workaround, and graph traversal is almost always from a top-down direction, in which the state is correct, but in a multi scale context with more complex hard dependencies, it might creep up more often.

[Samuel-amap]

I exposed this issue with a 5-model toy demo with a 3-layer, 3-model hard dependency and prototype code that was meant to iterate over all the hard dependency nodes to access their soft dependency ancestor.