ERP5Workflow: add variable to avoid multiple call to function and remove successive 'if/continue' for readability

ERP5Workflow: revert more changes (some Property Sheets have been moved to erp5_workflow bt5, they are back to product/ERP5/bootstrap)

- erp5_test_workflow
  *  add testWorklowMixin test case for inheritance purpose,
  *  move testWorklist ERP5 test to portal_component

author: Wenjie Zheng

- use mixin class to allow reusing common performance functions
- remove usage of quiet and run_all_test

Reduces the number of meaningless 404 errors.

so that we keep the query string in the redirect url if exists.

Instead of only having possibility to check when inventory will be below a reference_quantity,
allow to check when it will be higher.

This code is useful to run any unit test in a live instance. Until all products tests (like
ERP5/tests/*) are moved as components, this code is useful.

This reverts commit 9240d498.

also stop casting select_language to str.

If ERP5 Jupyter kernel tried to persist an object created from a new-style class, it would crash because the object has no `_p_jar`. This makes the creation of the ObjectWriter fails. This kind of object needs to be handled by (c)Pickle.

Related to bug report https://nexedi.erp5.net/bug_module/20160819-882FA2, created by @kasra.

@Tyagov, please review when possible. 

/reviewed-on nexedi/erp5!162

erp5_item: the purpose of getTrackingList or getCurrentTrackingList is to avoid passing simulation states by hand

Some tests where explicitely checking that transformation is not set in case
several are found. It is indeed better to ask user decision in such case.

mrp: a production order has a specialise link for business template, so we have to look for transformations