Reordering of augmented and direct children in containers

Some devices are unreasonably touchy about the order of children we send them – i.e. they expect to encounter direct container children before seeing any augmented children. While we push them to NormalizedNode builders in this order, the builders are using plain HashMaps (and rightfully so) to track them, which means they can get reordered. Based on this, the device doesn't accept the result sent from Netconf cause the order of  children is changed.