ERP5TypeTestCase.py: reactivate dynamicWorkflowConversion, log the type-workflow relation dictionary on log.

erp5_workflow: script to reassign workflow when there is a new bt installation after workflow conversion which may bring old assignment in chain_by_type with converted workflow ids.

erp5_ui_test: workflow history should generate 2 records for copy clone action in edit_workflow's history.

erp5_ui_test: after deploy new workflow, workflow histroy won't generate 2 recordes for edit_workflow when a new object is generated.

ERP5Site.py: shouldn't activate migrateToPortalWorkflowgit add product/ERP5/ERP5Site.pygit add product/ERP5/ERP5Site.py

This will ensure that all other gadgets in the page have been correctly instanciated.

ERP5TypeTestCase.py: avoid using accessor in dynamicWorkflowConversion. also put self.commit() back.

This list can be viewed in the panel History link

It prevents the getter to fail if a Person object has been reached from a relation property

This should have been added and handles twisted use cases such as:
  1. Install bt5 with ZODB Component C1 using version_priority V1.
  2. Install another bt5 adding version_priority V1.
  3. Install Portal Type using C1 as type_class.
  => No reset was done after 2., so C1 was not added to ZODB Component
     registry_dict (__registry_dict) and thus ignored.