Loosen the security on methods which we will use in erp5 catalog view in
restricted environment. As suggested by \@vpelletier, this should be
accepted as all methods were restricted by default earlier.

/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

just test for truth instead of checking in [list of false instance]

fix typos and remove unused variables.

Login_isPasswordValid is no longer used.

When reseting password through portal_password, we should check new
password comply with policy.

Because user is not logged in at this stage, we expose a new method
`PasswordTool.analyzePassword` that checks the password is valid for
this reset key.