Fixes Zope 2.13 .

make items tales expression generic in PaymentTransactionGroup_viewSelectPaymentTransactionLineListDialog/your_sign.

Otherwise, we use superclass' __contains__ implementation, which uses
objectIds, which is inefficient in HBTreeFolder2 to lookup a single key.

Revert "Change listbox to get the start_date from movement because the start_date is updated when the object is created. To be possible display the datetime customized the listbox_delivery_start_date was renamed to listbox_movement_start_date to follow the column used. One test was updated because name of the tag was changed"

This reverts commit 5424c208.

In this case, the test should be fixed instead of the proxieson erp5_core

Conflicts:

	bt5/erp5_ui_test/bt/revision
	product/ERP5/bootstrap/erp5_core/bt/revision

Test were moved to RenderJS's repository.

This runTestSuite uses "python setup.py test" to launch the tests at
a certain folder.

The runTestSuite can upload results using TaskDistribution.

This code is generic enough to be used by others libraries.

The code on ERP5TypeTestSuite is preserved for backward compatibility for
now, until it got updated.

Update now, force the reload of all alarm promises.

Ser periodicity_hour to 0 in addition with "everyday" frequency

Instead raise an exception, try..except to log incapability of resolve the algorithm

Update copyright, license and xml changes on erp5_workflow business template

This exception is required to be used in ZODB due erp5_promise.

The UI created use "Check Consistency" Name in other to keep compatibility with future implementations which are going to use Constraints and checkConsistency API.

In other to keep the promise, create an System Preference if no other were setupped.

Sometimes on configuration product-config can be defined but promise-path and
site id isn't, like for example when some instance use DeadlockDebugger.

Whitespaces shall be encoded with %digit

Those alarms read the promise parameters (configured for example by SlapOS) and
can configure ERP5 if user want to solve the difference.

  Read external promise parameters.

  The parameters should be provided by an external configuration file.
  Location of this configuration file is defined in the zope configuration
  file in a product_config named as the path of the ERP5 site.
  Example if the site id is erp5:
    <product-config /erp5>
      promise_path /tmp/promise.cfg
    </product-config>

  The promise configuration is a simple ConfigParser readable file (a list of
  section containing a list of string parameters.

  getPromiseParameter returns None if the parameter isn't found.