See merge request nexedi/erp5!1447

See merge request nexedi/erp5!1437

 * expose firefox console and error logs in `geckodriver.log`
 * expose `geckodriver.log` in the folder testnodes expose on http
 * fix some cases where test were detected as "did not run" and cases where "did not run" tests were not reported as failures

See merge request nexedi/erp5!1444

This is not really for errors during the test itself, but for errors when
ERP5TypeFunctionalTestCase manipulates browser to execute selenium test.

This depends on the support in slapos nexedi/slapos!999

It can happen that a test running selenium fail in python, but not in selenium,
like for example test_result_module/20210615-CDADEC14/183
To prevent such tests from being reported as PASS, we make the total number of
failures being the sum of the python unittest failures and the selenium failures.

It happens, for example with erp5_officejs_ui_test:testFunctionalOfficeJSPyodideNotebook
on test_result_module/20210615-CDADEC14/183 that the test is considered as
not running, because the test result table was not populated in time.

Add an explicit wait to prevent such problems.

This fixes commit ea4cb55b.

Our 'rmtree' helper has never been supposed to be called on a
non-existing folder: the ENOENT handling is an unrelated
implementation detail for Python 2.

Also drop erp5.util's rmtree and use the one from slapos.core,
which is a [testnode] dependency.

This front page gadget allows user to:
* create any kind of document
* launch any kind of report
* contribute a new documents

This gadget can be used to replicate the xhtml access page.

Eventhough _getBudgetDict was cached, getAvailableBudgetDict also
calculates getCurrentBudget for each cell, which is also heavy.

Duplicate actions are actions from the same category with the same name.

See merge request !1442

With software release test suites, there are probably
files/folders with permission issues.

See commit 380037f8.

so that we can access this log directly via http

This firefox setting cause console.log messages or javascript errors to be
printed on stdout, which should help diagnosing failures sometimes.

See merge request !1439

By setting XORG_LOCK_DIR, we can isolate processes when running on slapos test
nodes, so that instead of having all test runners used the shared /tmp, which
eventually fail with

    EnvironmentError: All displays locked : [':123', ':124', ':125', ...

errors when too many testnodes are currently running or too many testnodes have
left some stale lock files. Eventhough since fbdb4ec9 (test: Do not check
presence of lockfile in /tmp/ to assume Xvfb is running for this display, 2017-06-07)
things have improved, it happens that the lock files are owned by a different
unix user (because it was left by another testnode), then Xvfb is not able to
remove the stale lock file.

This is backward compatibility code for previous commit.

actions in erp5_jio_view category does not seem to be directly presented
to user, so rename them so that they don't use the same name "View" for
coding style test_DuplicateActions

Duplicate actions are actions from the same category with the same name.

`inst/test0-0`  ->  `i/0`

See merge request nexedi/erp5!1441

With bf57228a ([erp5_core] RelationField listbox must also fetch
default_params value from the relationfield, 2018-05-09), we introduced a
regression that listboxs from relation fields "proxy listbox ids" default params
where no longer used. As a result, if we have a listbox which define some
catalog search with default parameters, like for example the "Suppliers" or
"Clients" listboxs from erp5_trade are doing, these parameters were not
taken into account. In the case of trade listbox, this was showing all nodes.

This changes Base_getRelatedObjectParameter to get catalog search from the
proxy listbox if there is one.

trade_renderjs_ui_test: tests for "Suppliers", "Clients", "Organisations" and "Persons" Proxy Listbox Ids