If for some reasons loadClass was not working, it was failing totally
silently without any log. If there is any unexpected error in loadClass,
this ended up for example having some tests failing with :

RuntimeError: Malformed property definition <persistent broken
erp5.portal_type.Acquired Property instance '\x00\x00\x00\x00\x00\x00\x12\xb5'>
on /erp5/portal_property_sheets/SimpleItem

While only this was displayed in logs :

ERP5Type/dynamic/lazy_class.py", line 350, in loadClass
    class_definition = generatePortalTypeClass(site, portal_type)
...
AttributeError: __of__

Which was totally unrelated to the real problem.

So a silent initial error was the source of later unrelated errors, making
it very difficult to find the initial source of problem.

So make sure we have logs as soon as we are not able to load a class.

erp5_invoicing: Invoice Transaction Simulation Rule can also expand from Pay Sheet Rule (which is basically an invoice)

erp5_payroll_l10n_fr: adds new Types of Documents used to produce a French Social Declaration Report called DSN (Declaration Sociale Nominative)

The new modules are the Social Declaration Report Module itself,
and the Payroll Enrollment Record Module, to add some information
about every employee's working contract.

erp5_base: updates the Career view to add one new field to differentiate company and establishment, and one to attach records.

The item of produced resources must not be reused on consumed resources

in some rare cases, proxy was still alive for unknown reasons,
thus we had troubles to start a new one. some testnodes were failing
randomly because of this

This change solves the error which one gets while trying to access properties
Form for an ERP5 object having one or more of its property of type 'selection'
or 'multiple selection'.
For example: If you try to access property form for any portal_type objects,
you'll get an error : "'select_variable' is not defined". This is because of the
absence of the property 'select_variable' for the property of type multiple selection,
which in case of portal_type object is 'Property Sheet List'.

This is helpful for ERP5 views/forms which displays selection or multiple selection
type object.

ERP5 Subcategory: Remove '_'(underscore) from 'multiple_selection' subcategory in elmentary_type category.

Subcategory 'multiple_selection' has been renamed to 'multiple selection' to maintain consistency.
Earlier, whenever a new StandardCategory object was created with property_type 'multiple selection',
one needed to change the elementary type explicilty to use it to generate property setters and getters.
The example for this can be seen from this commit:
nexedi/erp5@fd738753
After this change, in the view, property type field couldn't recognize the property and displays
(???multiple selection).

Also, everywhere in erp5, list_types do mention 'multiple selction' and not 'multiple_selection'.
So, its better to maintain consistency in naming the subcategory.

Implement an ad-hoc responsive CSS for ERP5.
This CSS is generated with the LESS compiler (http://less2css.org/).

Create new ERP5 launcher, to break compatibility with officejs.
OfficeJS apps will be migrated one by one to the new CSS.

Instead of inspecting the content of mixin modules, which relies on already
imported module, use the same approach as Document (updateGlobals()), eg using
FS path so that even modules not already beforehand are not ignored.

Not changed by Ni or Sven in b1f5a740

When a Property Sheet with a ScriptConstraint (whose Document is a ZODB
Component) was added to Memcached Tool: Document Component was partially
loaded with no Property Sheet yet (and thus without the accessors needed
to import ScriptConstraint ZODB Component) and ScriptConstraint Document
was considered not available.

Changes from Ni Yan, and Sven Franck