This is for backward compatibility.

Also add some explicit tests for check_consistency, it was missing in
the first place.

by adding  timeout in order to prevent an error from changing page before
finishing loading the iframed setting gadget

When pusing to for_testrunner_1 branch, we often have this failure on testFormPrintoutAsODT:

```
======================================================================
FAIL: test_field_replacement_with_variable (testFormPrintoutAsODT.TestFormPrintoutAsODT)
test variables replacement in ODT documents.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/srv/slapgrid/slappart9/srv/testnode/zl/soft/4a13de8a0fdf926ddebab0387de0dc5e/parts/erp5/Products/ERP5OOo/tests/testFormPrintoutAsODT.py", line 1252, in test_field_replacement_with_variable
    self.assertEqual(node.text, value.strftime('%d/%m/%Y %H:%M:%S'))
AssertionError: '06/12/2010 11:33:15' != '06/12/2010 11:24:15'
```

After some investigation, turned out that:
* tests where always failing when running by `COMP-2544-3Nodes-ERP5PROJECT2` testnode
* This machine uses `SystemV/CST6CDT` as timezone
* the test fails in the same way when running locally with `TZ=SystemV/CST6CDT`

I belive this fixes, I tried running under `SystemV/CST6CDT`, `UTC` and `Europe/Paris`  TZ and it passes for all cases. 

/reviewed-on nexedi/erp5!174

/reviewed-on !175

Use of fail is now a coding crime

Since ODF dates are "timezone naïve", just calculate the timestamp with
the input date timezone as reference timezone.

I don't think the "XXX Works only if the timezone is the same in
OpenOffice" comment was true, so I just remove it.

It's better to explicitly specify the expected value, this test should
not depend on DateTime.strftime implementation, especially since this
implementation does some timezone conversion depending on time.tzname

this way after a zelenium tests ERP5Site_setupDummyMailHost this will
also reset the mails that could have been sent in previous tests.

This sends too many emails.

Some parts were outdated

The main purpose of these changes is to activate call to portal_sms.send; This way it is isolated it in a transaction that is less likely to fail. Activate with max_retry=0 and conflict_retry=False not to send activity twice in case of error.

There are other cleanups, see individuals commits.

/cc @seb @kazuhiko @gabriel 

/reviewed-on nexedi/erp5!49

Since sending email will not work without destination email, we can globally set this constaint

This way it is isolated it in a transaction that is less likely to fail. Activate with max_retry=0 and conflict_retry=False not to send activity twice in case of error.
As with email, if there was an error in activity processing, it is advised to investigate the transport logs to see if message was send or not.

event_simulation_workflow already call `send` type based method upon start transitions.
This workflow was not chained to portal_type, but if it would have been then message would be sent twice.

It allows to not cancel the loading of the iframe and to prepare the appcache.
The former behavior removed the iframe thus interrupting the preparation of
the appcache.

Putting field in center increases the string field size for ERP5JS

re-apply 25cd1201 that was mistakenly reverted by b847b45e

Hey @Nicolas can you please take a look at all this ?

All this started when I realised we probably do not want to allow grouping reference to be set when we have transactions from different ledgers ( edda8b58 ) and then realized it would be required to allow choosing ledger in grouping fast input instead of just showing all ledgers together ( d1ecbe29 ).

The rest are small changes to move out complex logic from TALES to a script and small fixups.

Thanks

/reviewed-on nexedi/erp5!170

This reverts commit b847b45e, reversing
changes made to 9075a38f.
The reverted commmit has been done automatically, investigation is needed

Putting field in center increases the string field size for ERP5JS