zope.{interface,component} implement Interfaces through __implements__,
__implemented__ (both implementedBy instances) and __provides__ (ClassProvides
instance) attributes set on the class itself through implementedByFallback
(zope.interface.declarations).

However, this implementation creates circular references by referencing the
class itself and thus erp5.* classes (and all its Accessors instances) were
never GC even after a reset.

When running testXHTML and installing the Unit Tests bt5s:
  * After 10 resets:  21MB leak (~  7% of Zope process USS).
  * After 20 resets:  70MB leak (~ 18% of Zope process USS).
  * After 28 resets: 122MB leak (~ 26% of Zope process USS).

Fixes browsing ERP5 documents without activity tables available.
Of course, as most modifications trigger activity creation, no
modifications are possible. But this improves read-only access in
degraded conditions.
Also, by design a successful query must return one line, so do not test
returned value before processing it.

Allows recovering from broken connection strings, as ERP5 authentication
still relies on having a working catalog.

erp5_travel_expense: Record creation is eventless

erp5_travel_expense: Representative Record creation is done by an alarm

Copypasta from the other MR [here](nexedi/erp5!230 (comment 22890)). I found a problem and tried again from scratch. I will close that Merge Request once this one has been approved...



@Tyagov
Currently, when running a Jupyter notebook using some types of imports leads to errors. With this fix the following ways to import things are working:
```python
import string                  # worked before fix
import string as s             # worked before fix
from string import ascii_lowercase             # worked before fix
from string import ascii_lowercase, ascii_uppercase, digits           # fixed - used to import only the first thing
from string import ascii_lowercase as a, ascii_uppercase as b         # fixed - used to give "Error at Server Side"
from string import *                                                  # fixed - used to give "Error at Server Side"
from string import Template                                           # works
```
This was happening because after executing every cell the code would move between SlapOS nodes and lose the imported modules/classes/stuff. This was partially fixed before, but this fix should cover all use cases. I have also added tests for these cases in testExecuteJupyter...

/reviewed-on nexedi/erp5!233

Otherwise, the portal_status_message is not correctly escaped, which can cause bugs with older web browsers. It happens when the translation of this messages in the user's language uses special characters

MonthlyRangeMovementGroup: make tested property list configurable, whose default is ('start_date', 'stop_date').

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'>)