JCR-2281: Loading all the properties into the cache causes undesirable side effects

Problem analysis:
- Some parts of the code (orderBefore + Remove + Same name sibling and import document view with UUID_COLLISION_REPLACE_EXISTING) could behave abnormally in case the cache contains all the properties of the target node, that is due to the fact that those parts of the code assume that we get the list of properties from the database which allows to have the correct path for the properties when we change the path of a node which is not true in case we get the list of properties from the cache because the path of the properties still have the old path.

Fix description:
- We make sure that the path of the properties matches with the expected/new path