Unify the versions at all bt5.

This prevent the field be named twice if the user selects raw parameter edition. In such case, we let the erp5 validate it instead.

On most of schemas, we are not strict with the format, so allow us be flexible, include additional fields for the user don't loose values if the schema changes.

Show states and allocation information on ERP5 UI, this make easier to Cloud Administrators navigate between the objects while investigate an incident.

This configuration would allow configure more easily an ecommerce ui.

This drops eventual dupplication at the code implementation.

  Some parameters has the same ids on connection_xml and parameter_xml,
  which makes in certain cases parameters always diference.

  The hash would simplify the comparations for slaves.

We may differenciate 2 groups of customers Suppliers and Consumers on which kind of products are possible to request on ecommerce interface.

   Sometimes the information comes much later them we expect, this
   prevents false positives and flacky tests

  Several packages has same namespace, this prevents fail if several
  slapos related packages are installed on the same machine.

Indroduce the possibility to request Slaves by respecting software definition ("shared").

tests on this method clouldn't reach updateCausalityState and updateSimulation with the condition portal_activities.countMessage(...) == 1