by evaluating it in a translationContext

Some report sections may be using translation.

Localizer.get_selected_language is only functional in response to user
requests. Saving it in Base_computeReportSection was already too late
because it's already an activity request.

This code was slightly different in three places:
 * Base_activateSimpleView: only use request.form.items()
 * Base_activateReport: use request.items()
 * Base_computeReportSection: use request.items()

request.items returns all items from request.other, request.form and
request.cookies.
In all cases, we are interested in request.form, so that report runs
with the same user input in request. We want to restore restore
request.other for Base_computeReportSection , but it does not harm in
other cases.
We always drop cookies to fix  #20180220-1DBF516 (as a consequence the
request will not strictly be identical, but rendering reports should not
depend on cookies)

on PostModule_createHTMLPostForSupportRequest

instead of PostModule_getAscendingRelatedPostListAsJson

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 !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: nexedi/erp5@5a0b3763 and nexedi/erp5@388a508b.


/reviewed-on nexedi/erp5!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.