Read resource operation handler does not preserve child order when registration has model overrides

Normally, the read resource operation returns children of a given type in their correct order. However, if the child type has overrides (e.g. type=foo overrides type=*), the read resource operation returns the override children first, followed by the wildcard children in order. Order should be respected for all children of a given type.