[442289] Rename distribute actions - Forgotten changes in plugin.xml

The constant changes have not been backported in plugin.xml.

Change-Id: Ifa4f0b23e660156655c25b47bc34beba32aaf836
Signed-off-by: Laurent Redor <laurent.redor@obeo.fr>
[test] Make sure the UI loop is processed when editor an is opened

We expect an editor opening to trigger UI processing, notably defered
arrange requests. We make sure the event loop is processed before moving
forward so that we don't have failures later on by processing it when
the editor is no longer available.

Change-Id: I77d19b7dcfffbe278c1de7f37de464078f1a010b
Signed-off-by: Cedric Brun <cedric.brun@obeo.fr>
[430724] Session.save will now postpone the save in post-commit

Bug: 430724
Signed-off-by: Cedric Brun <cedric.brun@obeo.fr>
Improve IsModifiedSavingPolicy to avoid False Positives

This adaptation of IsModifiedSavingPolicy is closer to the
SavingPolicyImpl strategy:
1. it uses the resource.isModified state as a basis to compute
what needs to be saved. Any resource marked has having been migrated
will also be considered "logically modified".
2. it browse the other resources to detect dependencies toward
resources which are modified
3. it filter this set of logically modified resources by serializing
them in a file buffer and comparing the result with the current file.

This strategy has the following characteristics :
- we avoid many serializations compared to the SavingPolicyImpl
  implementation by using the isModified boolean
- On the other hand we might browse the models, but this is made in a
  way that proxies should not be resolved. In practice this did not even
  came up in the profiling traces.
- we will never ever actually save the file if there is no change (just
  like the previous policy)
- If we *miss* a resource in the first step and don't consider it
logically modified whereas we should, its a bug and some resources might
not have been saved.

Also this commit makes sure only platform:/resources are considered
(which is important for CDOResources for instance, we don't need to
browse the model there, or Ecore resource with http:// URIs, we don't
need to send PUT on the Eclipse Server...)
It make sures non existing files will be saved anyway as their
"isModifed" status would not be enough for a resource which just got
created in memory for instance.
It also makes the IsModifiedSavingPolicy ignore resource.isLoaded
when deciding whether a resource has changes or not. This is necessary
to keep the same behavior as the reference policy.

Bug: 430724
Signed-off-by: Cedric Brun <cedric.brun@obeo.fr
Introduce a ResourceMigrationMarker

This marker might be attached to a Resource to indicate that
some automatic migration *might* have change the structure
of the model during the loading (with no isModified flag)

This forces the IsModifiedSavingPolicy to consider this resource as
"logically modified".

This marker is automatically removed when the resource is processed
by the saving policy which checked that the serialization has no
difference with the current file content.

Bug: 430724
Signed-off-by: Cedric Brun <cedric.brun@obeo.fr
Activate IsModifiedSavingPolicy by default

Bug: 430724
Signed-off-by: Cedric Brun <cedric.brun@obeo.fr
block concurrent accesses on Session internal state 

and stop sending notifications in an asynchrone way, in a job nobody
know when it will be scheduled.

For references, tickets which will need re-validation (might not be an
exhaustive list) :
VP-3150
VP-4151
VP-3605
VP-4166
VP-3371
VP-3605