Finegrained reloading of cached HstNode can result in wrong order of loaded nodes

A HstNode is a cacheable detached version of a JCR Node.

The HST model uses finegrained reloading when some jcr node changes in the hst configuration. However, this cached model can mix the order of the HstNodes differently than the order of the JCR nodes : This happens during a MOVE of a jcr node. The HST then gets an delete and create event from a jcr observer.

Reproduce: Make sure you have a site with multiple hst:sitemenu nodes below hst:sitemenus. For example the Hippo Connect / Campus site. Then, below one hst:sitemenu (don't pick the lowest one), move some sitemenuitem up or down. See that in the frontend, the entire hst:sitemenu now becomes last, even when it is not last below hst:sitemenus