Only mobyt support this parameter, so this break the compatibility with
essendex

Fix inconsistencies from gadgets

/cc @jerome 

/reviewed-on nexedi/erp5!225

erp5_knowledge_pad: Fix inconsistency with preferred_height and preferred_width in google_maps gadget

ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/google_maps (message: Attribute preferred_width should be of type string but is of type <type 'int'>)
ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/google_maps (message: Attribute preferred_height should be of type string but is of type <type 'int'>)

erp5_knowledge_pad: Fix inconsistency with preferred_height and preferred_width in google_calendar gadget

ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/google_calendar (message: Attribute preferred_width should be of type string but is of type <type 'int'>)
ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/google_calendar (message: Attribute preferred_height should be of type string but is of type <type 'int'>)

erp5_knowledge_pad: Fix inconsistency with preferred_height and preferred_width in google_search gadget

ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/google_search (message: Attribute preferred_width should be of type string but is of type <type 'int'>)
ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/google_search (message: Attribute preferred_height should be of type string but is of type <type 'int'>)

ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/clock (message: Attribute preferred_width should be of type string but is of type <type 'int'>)
ERP5Type.ConsistencyMessage for PropertyTypeValidity type_check on portal_gadgets/clock (message: Attribute preferred_height should be of type string but is of type <type 'int'>)

erp5_payroll_l10n_fr: reflects change in entreprise/employer from paysheets into the dialog aggregating paysheets for DSN social reports

/reviewed-on nexedi/erp5!229

erp5_calendar: Leave Request Period only use services as Resource

erp5_travel_expense: In expense report, remove useless rsvp.queue, do not overwrite special character

synchronize automatically data block web site

A Localisation Record is created when submit a expense record
only one received localisation record per user

erp5_travel_expense: localisation search should not prevent image preview

erp5_travel_expense: make sure localisation gadget is loaded

erp5_travel_expense: don't create localisation record when location is undefined

erp5_travel_expense: naming convention

erp5_travel_expense: Have Projects availables in Expense, define group on images and set source_section

epr5_payroll: update social_declaration view as transactions can be aggregated by several social declarations

It will allow to differenciate the Employer for which the Employee is working, and the Company to which the accounting and the payment are related

This reverts commit 6b6f1fe0.

This reverts commit 003e34c7.

The resource-to-account relationship is intended to be declared by
predicates (which are used here), but should only be explicitely set on
movements when they *differ* from these rules, as special overrides.
So, setting default accounts on movement is unnecessary work:
- predicate lookup is expensive, and business-model-specific shortcuts may
  be available which such generic implementation cannot implement
- multiplying unneeded relationships increases category table size, which
  is generally detrimental to performances