The code was not working as expected when we had several test nodes with same name
(which should not happen). So add a timestamp in the title.

test_result: fixed random issues where test result was staying confirmed while all tests were finished

When two test results line were stopped in parallel, both transactions were thinking that
there was still one ongoing test line, thus none of them were setting the test result in stopped.

Use activities instead of serialization to avoid having testnode getting conflict errors.

This makes a difference for SQLDict as not all messages are accepted for
insertion.

Firefox and Xvfb aren not provided by the tested SR,
but rather by a separate SR that is installed by the testnode.

Charting libraries are better within iframe to avoid enabling too permissive
Content Security Policy globally

Fix error display after save
Fix parameters not recognized
Fix python linting
the same way as ERP5 Script Python

Add PortalType field to distinguish different types of Python Scripts, add referencence and use source code editor

We could not find a portable way to use verifyElementPositionRangeTop.

See internal discussion `[test][erp5] update selenium test` for more
details.

In addition to TypeEror when a 'date' is given, this also accepts duration=0.

If Test Result is associated with Test Node and thus distributor, and
distributor defines process timeout use this timeout to now when to
restart test lines. This is useful to avoid needless restart of tests
running on nodes related to long time outing distributors.

Otherwise fallback to default.

This link allows to navigate from Test Result via its Test Result Node
to Test Node and distributor related to given Test Result.

Note: It happens only, if client will do subscribeNode before calling
createTestResult.

This is accompanying commit to "erp5_test_result: stop affecting last
remaining tests to all test nodes", where alarms redrafts running tests
for long running nodes.

In case of very long running test nodes, to which support is introduced
in this work, it is acceptable situation that test will get redrafted
and shall be stopped.

Unfinished test
(test_18_checkConfigurationGenerationERP5ScalabilityDistributor) uses
return value of subscribeNode and assumes it is ERP5 object.

This work changes return value of subscribeNode to JSON object,
following startTestSuite return value, thus rendering this test failure.

As test is unfinished, non asserting part has been commented out.

Also if process_timeout is available in received configuration setup
process_manager with transmitted value.

Backward compatibility is assured, that if no process_timeout is
provided, nothing is being updated.

Also process_timeout not set on master (the default), will not change
local default.

Extend subscribeNode to send configuration provided by user.

ERP5ProjectUnitTestDistributor allows to define maximum process timeout
of testnodes attached to it.

Sending mode is set by user when printing the DSN report

Allows reducing the number of user existence check queries from one per
document to one per document batch, reducing database (currently, catalog)
latency effect on indexation time.
Also, avoid object -> id -> object dance for SQLCatalog instance while at
it.
Also, modernise syntax a bit, avoiding intermediate locals mostly.

These are used nowhere in the code. In many workflows, these
"catalog-available" variables are only configured so they appear as fields on
worklist definitions. So it is understood as more of an informative setting
having a local effect than a normative one having an effect on how
indexation happens.
So shave off a bit of useless time spent in indexation.
Also, it should be mentionned that when profiling this code causes a big
red-herring: this code is the first place where workflow history gets
loaded (and presumably indexed document itself), which draws attention
away from potentially more interesting areas.