fix manage_afterClone protocol to conform with zope implementation and fix cloning transformation bug using this new protocol
In Zope OFS' manage_afterClone suports an item argumetn that is set to the object actually being copied.
After this change, _afterClone scripts are called recursively and item argument is passed so that objects and subobjects being cloned implement different behaviours in _afterClone depending on the object itself is being cloned or a parent object is cloned
The second part of the patch set is a bug fix for https://nexedi.erp5.net/bug_module/20160719-1B69F57 that needed this change.
test results: https://nexedi.erp5.net/test_result_module/20160725-3FCD91E7 (the failures are unrelated, I started this branch on a buggy master).
I don't know who can review that ... @gabriel @kazuhiko @romain any objections ?