split SupportRequest_getSupportTypeList with another script called
SupportRequest_getSupportTypeListFromProjectValue

Prevent failure when opening the submit support request form.
If the first project has no related sale supply, the form rendering
was failing.

- testnode saves in its config the repositories paths
- minor refactoring and cleanup

/reviewed-on nexedi/erp5!606

Small recent change to handle cookies in connections to frontend urls.
* The refactoring of old testbrowser version was already reviewed and merge to master: 5a0b3763 and 388a508b.


/reviewed-on !587

- Thread classes to run commands and collect metrics for tests.
- Refactoring in benchmark process and result

/reviewed-on nexedi/erp5!588

- the commands to run the tests are launched using threads
- a thread is used to ask instance for metrics periodically
- refactoring for a more generic code
- refactoring in log handling
- old code related to created documents and create users removed
- new script parameters
- general refactoring and cleanup

- hardcoded software release url removed (http with password protection for now)
- scalability runner handles frontend request. It asks for a local master frontend apache software installation and instance request.
- testsuite brings the urls corresponding to instance, bootstrap, metrics collection.
- vinculation between scalability runner and runScalability script. Process manager is used to run the script as a command.
- scalability runner manages the test result cases and loops among different testsuite configurations.
- userhosts software is used to run the command for the runScalability script, to solve DNS.
- refactoring according to last changes in TaskDistribution
- general refactoring and cleanup

- communicator considers requests of master frontend and instance destruction.
- communicator retrieves frontend related information from instances.
- minor refactoring and code cleanup.

Use the filter editor to select the domain in a select input.
This concentrate all search parameters in only place to improve the usability and discovery.

erp5_trade: Proxify my_ledger to Base_viewTradeFieldLibrary as it should have always been (06f701a4).

This fixes TestXHTML.test_configurationOfFieldLirary Unit Test failure:
  Assertionerror: 1 fields to modify
  erp5_trade/TradeModelPath_view/my_ledger: Unproxify Field

erp5_trade: my_ledger.items=Delivery_getLedgerItemList as all other erp5_trade my_ledger fields (06f701a4).

newContent already must reindex created documents, no need to explicitly
request it.

Although these are synonyms here now, it may evolve in the future.

Some underscore-prefixed properties may fail callable() check (ex: because
the document requires some properties set to access an underlying actual
callable).
So give these a chance to be skipped before failing.

[erp5_odt_style] [renderjs_ui] Allow global Print action from ODT style only on Documents and not Modules


-  split Print action into two and set object_jio_print only the one for Documents
-  add all possible actions to activate the "Export" button

/reviewed-on nexedi/erp5!600

erp5_real_time_inventory_accounting: Split the BP into dedicated ones for Sale, Purchase and Internal.

Checking 'delivery' portal_type for PL type will not work on real
implementations as the PL is not built during the first expand and
expand_related=0 after and this is how it should be done anyway.

Same as IPL use case.

IPL must expand both "In"coming (only PPL until now) and "Out"going (only SPL
until now) SMs, so split up ledger='stock' TMPs and add accordingly two
subcategories to stock ("entree" and "sortie").

Also instead of using 'use' categories everywhere (TMPs and Rules), use the
Delivery Portal Type as this makes things clearer for IPL use case.

This is enough for now to handle both Outgoing/Incoming/Transit use cases.

This implements Outgoing/Incoming Accounting Rules and Builders.

This column is not a significant condition for this test. It is an
unreliable transient piece of information intended for a human observer
monitoring activity execution. processing_node is the reliable piece of
information this test should care about.

For when redundant activities may be skipped.

By providing a method id receiving considered document and activate_kw as
parameters, and producing a new activate_kw value.

Julien Muchembled:
- ExceptionRaised class simplicitation