Renaming pages having children with relations won't update the reverse relations

Simple refactoring is supported via a listener listening to DocumentCreatedEvent. In the general case, by checking if the JobStartedEvent has type "refactoring/rename", the listener updates the inverse relations of a renamed page, by looking into the "entityReferences" property of the request associated with the current job: see PageRelationsRenameEventListene#L113.

However this trick does seem to work when the renamed page has children that have relations, and it seems that a real DocumentRenamedEvent with an explicit destination / source would be needed. A RenameJob exists, but we may need a DocumentRenamedEvent with a clear source / destination for solving this issue.