creating a guard when all the informations are already in properties
of the object is useless, these guards were forgotten

in testERP5Workflow, a test was failing due to changes in
storage of expressions (we now store the expression object
so we don't have to recompile the expression all the time)

the only way to escape the 'while 1' loop was depending on changes on the state
variable, which was, before this fix, using the invariant tdef instead of
transition

a few useless methods

in order to remove hardcoded 'transition_' or 'script_'

this file has already been moved to erp5_core

with old DCWorkflow, portal_workflow could contain the chain_dict for portal_type/workflow
association

this is a wrapper for the PythonScript __call__ method
It should fix testSecurity

This fixes testListboxToolBarDelete failure in testFunctionalKM

keep it as compatibility code but also search for new workflow/portal_type association
directly in portal_type (type_workflow_list)
This fixes some failures in testFunctionalCore

if using id, it would check for simulation state to be for example in state_draft (id)
instead of draft (reference)
This was breaking testFunctionalCore page_templates_zuite/testSearchDialog

testERP5Catalog was failing because there was more than 1000 activities in portal_activities
and the one that should have been invoked was at the end of the list
set the limit to None, and only check the interesting activities
Also, add SQLCatalog_deferFullTextIndexActivity to activities to
play.

this test is no more relevant because chain_dict is not used anymore
and portal type/workflow association is done in portal types directly

don't try to remove non-existing worklists!
+ use getPortalType instead of __class__.__name__
+ only test guard on ERP5Worklow worklists

that are not used anymore (workflow are associated
to portal_types in portal_types directly)

non-existing getWorklistValueDict one
+ add getGuardRoleList method on DCWorkflow worklists