this was not working either when testnode does not pass log_directory

the case where --log_directory was not passed was not properly supported

error in the merge

Test nodes already share a folder with a `suite.log` (and a quick and dirty application to view the log live).

The path of this folder is now passed to test runner so that they can also put some log files there. 

ERP5 test runner uses it by writing the `Z2.log` and `zLOG.log` on the running tests there. 

Slapos SR tests also uses it.

See merge request !948

From there we can now access zLOG.log and Z2.log for erp5 and snapshots
from slapos software release tests

Just propagate it as SLAPOS_TEST_LOG_DIRECTORY, then tests (running with
python setup.py test) will be able to use it if they wish.

Each runUnitTest will use a subdirectory in the log directory used by
runTestSuite.

Log files will be created in this directory.

This way, test suite can place some log files in this directory, so that
we can inspect when tests are running.

ZODB Components: Monkey patch astroid: Namespace package handling only considered the top-level module.

This did not work with Shared.DC.ZRDB (Shared.DC namespace package) as it only
considers Shared to be a namespace package and not Shared.DC:
  No name 'ZRDB' in module 'Shared.DC' (no-name-in-module)

Also include an upgrader to simplify site upgrade.

ZODB Components: Migrate Delivery Document to erp5_core (not erp5_trade as it is used everywhere) (MR !1107).

* Project Report: Removed (deprecated 14 years ago over Task Report).
  + Remove Expense{Module,Line}_view* as these use Project Report and Project Report Line.

* Move Documents used by several bt5 to erp5_core rather than add depends on erp5_core.
  Once migration of Products to ZODB Components will be finished, there will be moved to
  their appropriate bt5s as it would be complicated to reorganize bt5s too at this point:
  + DeliveryCell: used by InvoiceCell Document.
  + DeliveryLine: used by erp5_ui_test.
  + InventoryCell: used by erp5_archive.
  + InventoryLine: used by erp5_accounting.

* This prevents migrating Inventory{Line,Cell} to ZODB Components as Interactor
  are imported early at startup where erp5.component is not available yet.
* More generally, Interactor should probably be replaced by Interaction Workflow
  for ERP5 objects but in this case, override is enough as it is done likewise
  everywhere else.

Now that getInterfaceTypeList also return file system interface, we can
use it directly.

Also simplify a bit by not getting types tool multiple times.

One breaking change is that for an interface like ISomething, ISomething
is no longer a valid prefix, only Something. So scripts like
ISomething_getSomething are not valid, only Something_getSomething.

`self` argument should not be a cache key, otherwise we have one cache
per skin

RESPONSE.write cannot be used with WSGI, so use another trick to return
a response without commiting the transaction.

* Remove TaxLine Document which was replaced by Trade Model Line a while ago.
* Keep {Delivery,Inventory,Order}{Cell,Line} on FS for now because of InventoryInteractor.
* About DeliveryRootSimulation Document migration to erp5_trade:
  + AccountingTransactionRootSimulationRule (erp5_accounting) inherited from
    it but as this is probably not actually used/useful, avoid depending on
    erp5_trade or refactoring but just copy/paste.
  + InvoiceRootSimulationRule inherited from it but as it is only used in
    erp5_invoicing (which already depends on erp5_trade) move it there.
    - erp5_configurator_standard_accounting_template: Add depend on erp5_invoicing.
* Move Documents used by several bt5 to erp5_core rather than add depends on erp5_core.
  Once migration of Products to ZODB Components will be finished, there will be moved to
  their appropriate bt5s as it would be complicated to reorganize bt5s too at this point.
  + Inventory: used by erp5_archive and erp5_accounting.
  + Order: used by erp5_project.
  + PackingList: used by erp5_publication.

* Add bt5 dependencies:
  + erp5_demo_maxma_rule: Invoice*Rule rules.
* Move Documents used by several bt5 to erp5_core rather than add depends on erp5_core.
  Once migration of Products to ZODB Components will be finished, there will be moved to
  their appropriate bt5s as it would be complicated to reorganize bt5s too at this point.
  + Invoice{Line,Cell}: used by erp5_payroll.

Clicking on a button tag with an embedded img tag crashes everything.
The right way to fix this is probably to drop the img tag and use a CSS background url instead.

Prevent sending the binary each time.
Follow file input behaviour

There's not only one "login of a person", so it's better to show nothing
at all here.

we can delegate "editable", it's the default value of
my_view_mode_read_only_default_credential_question_answer

This category never existed and this is always logging:

    Base Category 'package_type' is missing. Accessors can not be generated.

Since catalog is migrated to an ERP5 document and can only be edited
with ERP5 UI we lost the hability to define security uid column for
default group, which is supposed to be defined with an empty string,
something like: `  | security_uid`.

Enable whitespace preserve on this field to allow saving this string
string without being stripped by formulator.

it seems de2545fc was supposed to be a
rename.

Otherwise indentation is lost when commit from erp5_vcs interface

Python scripts can be used as catalog methods, including as "clear catalog"
methods. This was causing error when upgradeSchema was called:

    product/ERP5Catalog/CatalogTool.py", line 1372, in upgradeSchema
      method_list_by_connection_id[method.connection_id].append(method)
    AttributeError: connection_id