do not force the user to check the box...

during workflow conversion
On DCWorkflow states, when the workflow does not manage permissions,
they may appear in some states's permission_roles dict.
This create wrong permissions, and we should not set them if they are
not managed by the workflow.

remove duplicated code

not by category because the script used here are from portal_skins
moreover, they are not put into the workflow object (and thus accessible in the ZODB)
because the same script is often used in transitions from different configurator workflows

this will allow the use of proxy_roles
fixes, among others, broken tests on packing list

the private setters are called by methods like 'edit', ...

ERP5Workflow: replace use of old Variable type by Workflow Variable in erp5_configurator_ebusiness_lotse

call scripts by their old name

they don't require another bt to be installed and they are here for this purpose

ERP5Workflow: add acquire_permission_list attribute, setup acquisition of permission/roles correctly when converting, rename methods

and remove state_permission_roles property

it should not be required to have destination list on a state

WIP
todo: remove property in property sheet
persistent mapping will take care of changes on the dict and commit them in the ZODB
otherwise, because we change the attributes of the dict and not of the State object,
the changes will be lost

during workflow conversion, when original workflow permission_roles is
None

state_permission_roles attributes should be updated when the permission list is changed on the workflow
it also fix matrixbox edition (was crashing when permissions where added)

+ remove unused dependencies

instead of re-coding the wheel