Re-index subtree on move

[peterkeung]

Currently, eZ Find does not re-index a node's subtree when the node is moved. This PR uses the same strategy that we use when the node's visibility is toggled, which is to defer the re-index to the ezfindindexsubtree cronjob.

[gggeek]

should this be made optional via an ini setting? normally a content in Solr does not carry info about all its grandparents... or does it ?

[pkamps]

@gggeek The node path is in the index, right? So solr searches using the node path will return funny results.

+1

[peterkeung]

Correct, there is at least path and visibility information to update, so I don't think this should be optional.