(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.

This is much faster, eg defining a max function is about 39 times faster and
even more on more complicated code:

$ python -mtimeit -s 'code = "def max(a, b): return a > b and a or b"' 'exec code'
10000 loops, best of 3: 25.2 usec per loop
$ python -mtimeit -s 'code = compile("def max(a, b): return a > b and a or b", "<string>", "exec")' 'exec code'
1000000 loops, best of 3: 0.632 usec per loop

Another reason is for traceback/pdb readability as __file__ is displayed in
the backtrace, but with 'exec' __file__ equals to '<string>', compile() allows
to specify a readable name easily without having to override __file__.

Also, set __file__ to the Component relative URL instead of the ID for
readability sake.

Signed-off-by: Julien Muchembled <jm@nexedi.com>

Fixes unittest.expectedFailure usage, allowing phasing out
backportUnittest gradually (at least for the backport part).

because they raise "The operation is insecure" error in recent Firefox.

- It causes the movements to be created in another delivery if the start/stop dates are different from invoice date

The code wrongly assumed that the .py file (containing source code of a
Component) was on the filesystem upon import but importing from an archive
uses tarfile and does not extract anything...

Get rid of refactoring/convention/spurious messages (ERP5 Naming Convention
may be added later on). Also, Pylint cannot deal with dynamic accessor/module
generation, so disable these error messages as well.

Also, patch pylint to handle try/except for modules imports
(https://www.logilab.org/ticket/9386).

Likewise Pylint, compile() has no side effects as it juste compile source into
a code object which may be passed to 'exec'.

Pylint should be enough and has no side effects...