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

and remove AccountingTransactionLine_getParentUrl which is not used

This reverts commit 5ec2f886.

While launching an new portal component test, a "Duplicate tpc_begin
calls for same transaction" error was raised. This was coming from
the finally clause in runUnitTestList, in the commit of
ProcessingNodeTestCase.unregisterNode.

After long investigations, we found out that a new app was created
while the transaction was still opened. After more investigations,
it was discovered that the runUnitTestList code was raising an
exception, and this exception was hidden by the exception in the
finally close.

So this patch provides:
1 - a cancellation of the transaction to avoid "duplicate tpc_begin
    calls" error.
2 - a print of the exception before the finally clause is launched
    to make sure we have information on possible exceptions