This reverts commit 264459a7.

Sorting by title on the module listboxes does not make sense because of the
way of the default title generation.  (ex SO-1,..SO-100 are sorted SO-1, SO-10)

Also, specify missing CountMethod in the listboxes.

erp5_autocompletion_ui: Increase delay before searching from 300ms (default) to 600ms, this should be enough...

For example, MultiRelationStringField does not return a plain value, but a
MultiRelationEditor overriding Base_edit default behavior.

So, Relation Fields in ListBox were ignored during validation as the input
value is compared with the current (default), thus the field could not be
cleared as the value from the actual object was not retrieved at all.

erp5_jquery_ui: As jquery-ui is imported straightaway, license should have always been jquery-ui one.

This reverts commit 3f8b6a39.
Also revert "fix a typo. potral -> portal."
(commit fa7113c9)

*_path parameters are preferred at SimulationTool level over UIDs, and
may not work as intended.

so that we can call it from restricted environment.

* now Selection for anonymous is stored per its content and its key is embedded in ListBox rendering.
* we no longer provide cookie to each anonymous user.
* thus same URL (i.e. same parameter) for any anonymous user should have the same result.
* Selection storage for anonymous can be still different from the storage for the normal users.

see http://docs.python.org/2/library/unittest.html#deprecated-aliases

(thanks Rafael)

Simulation Movements use 'causality' to link to different portal types:
- Business Link
- Trade Model Path
- amount generator line/cell

Only Business Links implement getCompletedStateList.

The initial 'exec' traceback was not passed when raising ImportError (following
PEP-302), thus it displayed traceback in component_package instead of the actual
location of the error. Also, Caching source code retrieved from traceback/(i)pdb
(through get_source()) was done after the actual 'exec', whereas it should have
always been *before* obviously...

Steps to reproduce:
  1/ Create and validate a Test Component A importing another Component B.
  2/ Invalidate Component B or add a typo not handled by pylint (because of exceptions).

Using DeadlockDebugguer lead to a deadlock when trying to debug a deadlock on
ZODB Component as it was trying to load the Component. Moreover, this required
accessing to ERP5 Site whereas DeadlockDebugguer is used outside.

Steps to reproduce:
  1. Create an Extension Component with a sleep and run it.
  2. Call manage_debug_threads.