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.

When checking constraints, ignore lines where the node is an acquired
organisation, we should only consider lines where node is an account.

removing lines, columns and tabs but improving PaySheetLine_asCellRange

These methods were generated when rendering the ListBox and with the id
of the ListBox in their name. However, a customer reported the following
problem on Accounting Periods ListBox:

  1. Display Accounting Period ListBox on ZEO-1.
       => The ListBox will be rendered and 'listbox_period_list_*' methods will be generated on ZEO-1.
  2.  Click on 'Next Page' button and the user is redirect to ZEO-2 where the ListBox has never been generated.
       => The method does not exist yet and thus a 404 error is raised.

Instead of having one method per ListBox ID, only one is now created (eg
listbox_setPage() for SelectionTool.setPage()) at Zope startup and the
ListBox ID previously defined in the method name is now defined in the
value attributes of the buttons.

Pattern: SIT_1 => RSPL => SIT_1.

Also, this reduces the complexity by not checking objects twice.

Functional Tests: Migration to PDF.js in recent Firefox clears preference to save automatically PDF files to the disk.

- <a href="c"> was not transformed to absolute url
- split the WebPage_exportAsSingleFile and WebPage_extractReferredObjectDict
into two scripts to allow to evaluate string html data.
+ tests

/reviewed-on nexedi/erp5!180

/reviewed-on nexedi/erp5!167

If we don't propagate movement_list_mode to catalog, this prevents
catalog from raising an error about this unknown parameter.

It's better to create new objects using same script rather than
keeping 2 scripts that try to do the same thing: Folder_create
(script used to add in case we create new object using the icon next to actions bar)
did not support the getRedirectParameter API. We now do all the work
related to adding new object in Folder_create itself.


Test Result : https://nexedi.erp5.net/test_result_module/20161006-39C681E1
Reviewed by: @jm 

/reviewed-on nexedi/erp5!177

This is for backward compatibility.

Also add some explicit tests for check_consistency, it was missing in
the first place.

by adding  timeout in order to prevent an error from changing page before
finishing loading the iframed setting gadget