they were originally named before_script and after_script and some
old names remained

+ rename field my_destination_title to my_destination to avoid using magic

missing "my_"

dynamic_class_generation_interaction_workflow

need to be investigated

this property seems not to be used on ERP5 in old DC workflow

- change guard-related description to be more clear and consistent
- remove expression from Transition view
- show right guard properties (were renamed)

fix Workflow creation/removal

Adding List to the end of the getter of a given property will return
an instance of type list.

for naming consistency

- Worklist
- Transition
- Interaction
- ConfigurationTransition

when in portal_component, got bootstrapping errors
removed non ASCII character in ScriptConstraint.py

WorkflowTool use a Script Constraint property, so it has to be define
when Script Constraint are defined (in erp5_core), not in erp5_property_sheets
because this bt5 is loaded before erp5_core.

to erp5_property_sheets as expected

having empty my_for_status.xml file was leading to ExportError

- move group to propertysheet Guard/guard_group
- move permission to propertysheet Guard/guard_permission
- move expression to propertysheet Guard/guard_expression
- move role to propertysheet Guard/guard_role
- remove description (portal type Variable should use Property sheet DublinCore instead)
- move automatic_update to propertysheet WorkflowVariable/automatic_update
- remove for_catalog
- move for_status to propertysheet WorkflowVariable/status_included