Allows FormBox to contain fields outside "left" group.
The use of this is most evident when FormBox is in the "bottom" group: it
allows included form to have field groups with borders (left, right,
center) or without borders (bottom), hence allowing competely extending
base form. This required rewriting JS code stitching "left" & "right"
groups together so it honours nesting.
For backward compatibility, hide "left" groups rendered inside any bordered
group - but only when there is no field in "right" group.
Also, clean up duplicated code in embedded_form_render and use proper
naming (templates used by forms should always end with "_view").

And add a test checking this in portal_rules

- PEP 308: Conditional Expressions
- PEP 341: Unified try/except/finally
- PEP 343: The ‘with’ statement

Checked following occurrences in comments:
- "Python 2.[456]"
- "Zope 2.[891]"
- "BBB"
- "BACK"

Checked uses of:
- email, hashlib, numpy & tarfile (modules)
- ImportError
- string.Template
- suppress_events (parameter of _setObject)

Excluded:
- some forked modules (MailTemplates, PortalTransforms...)
- some i18n compatibility code

This allows to Specify a random sleep time (with 'sleep' parameter) to
get more realistic results. Update the example accordingly.

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.