Both for _identity_criterion and _range_criterion

Add tests showing direct criteria specification in predicate scripts

And rule tests to match on simulation movements, since this is what rules match
most of the time.

Avoid concatenation of None and string vlaues if profile_path is defined later in vcs_repository_list.

Dates in signature have to be in %Y%m%d format.

Note: Signatures still do not match.

refactor code to be possible pass the parameter bt5_path to runTestSuite. With this, runTestSuite script can propagate this parameter to runUnitTest script

Fix the issue that a Invoice document can wrongly have a needless Root Applied Rule when it is created by Delivery Builder with a site which has many activity nodes.

Also document method a bit.

Instead of doing analysis of passed dict, just accept payzen_dict, which will
be blindly applied.

Split to more methods, in order to have proper separation and being able to
test critical parts.

How data will be corelated with service shall be implemented on caller level.
Thanks to this no additional requirements are added.

Allow to pass page_template which will be run in context of temporary object
with all required parameters.

Delegate responsiblity of dynamic data preparation to caller, check only service
consistency.

This reverts commit a91456c9.

Conflicts:

	bt5/erp5_payzen_secure_payment/bt/revision

This reverts commit e5b9bfac.

This reverts commit e1356f85.

It is required to give maximum extensibility to web site developer of payzen
based shop.

And so depends on erp5_tiosafe_core Business Template.

Those are all found properties which seems to be "static" for one payment
service.

Follows:
  * http://www.payzen.eu/integration/document/2.2Guide_d_implementation_formulaire_paiement_V2-1-ENG-Payzen.pdf
  * http://www.payzen.eu/integration/document/Guide_technique_d_implementation_standardWebservices_Payzen_ENG.pdf
  * http://www.payzen.eu/integration/document/2.2_Guide_d_implementation_formulaire_Paiement_V2_Parametrage_Avance_Payzen_ENG.pdf

In case of reused properties use their original name.

In case of payzen properties, use thier full name with payzen_ prefix.

This fix issues when we transfer characters not allowed in xml