One dependency less.

To enable DeadlockDebugger in test, we setup a default product_config,
and this was breaking testBusinessTemplate and testDynamicClassGeneration.
Also, stop duplicating code and use a mixin class for the "login" mehtod
used by both tests.

Since DeadlockDebugger is checking for product configuration,
it was no longer working in unit test

- the import dialog must show the url to import
- url should not be editable directly on review since it needs special dialog

If we ever need it back, just move this Document class into a business template,
so that Products.ExtFile is not a hard dependency of ERP5.

Import of javascript files coming from business templates was
sometimes altering the javascript source code.
It happened that javascript files with a line like
"  ];\n" was replaced by "];\n", so the indent was lost.
May be there is more beautiful ways to fix this.

We should have a way to 'purge' localStorage by setting a ROOT_CACHE_ID (which can be changed server side)

- display the output of all commands launched by erp5testnode in
  erp5testnode log
- add a thread to upload ongoing logs to the master regularly
- if the software release is not built successfully after a
  few time, totally erase software. This help unblocking if
  buildout is unable to update software.
- check if the last test result was cancelled in order to
  allow relaunching test without restarting testnode
- improve logs to allow much better understanding of what is
  going on

When the same document is uploaded,  the message displayed after upload is different. So, the code was changed to check the url without the parameters.

Use a much wider range for Accounting Period definition to prevent
random errors when define dates at the test.

The related tests were updated for check this change.

The reusage permit use configuration for multiple gap
definitions. Included specific test for Account Configurator Item.

This Constraint do not work for packing lists because according to
the constraint the "lines" should be order movements and not delivery
movements. Update related Test.

This keeps compatibitility with Standard Configurator outcome.

Test were updated to check the change.

The test should be compatible with Configurator Outcome and w/o
Configurator case. This change unify outcome of those 2 cases,
making it compatible when run into diferent scenarios.

This Configurator Item configures the script ERP5Site_getSecurityCategoryMapping, This can be
combined with roles generations and categories spreadsheet in future to generate full security
definition.

Update configuration to use Security Category Mapping Configurator Item instead include the
script directly, otherwise it breaks the instance due the dependency with scripts on erp5_dms

Initial code is almost the same as the one provided by erp5_simulation_test
in order to preserver initial compatibility

Those functional tests also need those business templates with the code
previously on erp5_simulation_test

Include base categories copied from erp5_trade in order to
drop installation dependencies. This permit the configurator
test become more accurate with the desired result.

Use sale trade condition from configurator or create a very
similar one. Do not use path to this in order to prevent
this business template depends on others bt5s.

Clean up some paths (**) which were useless (it adds nothing).