(ui) Create a new class to manage all updates related to move actions
(refactoring) ChangesFactory doesn't need a resourceSet
(refactoring) Start to add the new logic to ChangesFactory

First step for factory evolution: it should be able to manage correctly
changes in many files, even if more than 1 replacement must be applied
in one file
(refactoring) Implements Replacement classes
(refactoring) Basically perform all updates when cal files are moved
(refactoring) MoveParticipant is able to update packages in cal files
(refactoring) merge computeResults and getAllChanges methods

Also configure correctly title of post move Change object
(refactoring) Change the move refactoring process order
(refactoring) Allow to move networks
(refactoring) Allow moving diagram files (alone or with their network)
(refactoring) Ensure replacement will works in all case

This commit handle the specific case when many files are moved and at
least one of the files have to be updated (because it references another
file in the same list)
(refactoring) Clean: delete useless move participants
(refactoring) Clean: CalRenameParticipant use new ChangesFactory methods
(refactoring) Update MoveParticipants to use new methods (1/2)
(refactoring) Update MoveParticipants to use new methods (2/2)
(refactoring) Clean useless code
(refactoring) Rename: display an error when suffix has been forgotten
(refactoring) Fix bug when moverd files have to be also updated
(refactoring) Minor fixes
(refactoring) Split ChangesFactory.getAllChanges() in 3 methods

This will allows to reuse some methods later.
Move the clearReplacementMaps() call to the initialization
of each refactoring participant (and rename this method)
Already moved files are not managed anymore in getAllChanges()