Allow to configure testnode's process timeout from Test Master

ERP5ProjectUnitTestDistributor_view is extended to define non-default process timeout of script run by runTestNode. The testnode fetches this information during subscribeNode and so the test master user is able to define timeout of the used runTestSuite script.

Typical use case is a test node running VM with intensive and long running tasks inside the VM, which often take more then 10hrs to do the job.

The testTaskDistribution has been extended to check the transmitted value and adapted to new return value.

Things to be done:

• add a test proving that by using API it is possible to stop draft test result line on started test result
• check test for testnode inside of erp5.util egg
  • no test added, as this part of code is not tested
• proxify ERP5ProjectUnitTestDistributor_view/my_process_timeout
• DONE: https://lab.nexedi.com/nexedi/erp5/commit/121d85077f88a943b52ad9f8dd2575108a3b96a8
• link Test Result with Test Suite using specialise category
• really it means linking Test Result Node to Test Nodes (which go to distributor)
• DONE: https://lab.nexedi.com/nexedi/erp5/commit/fed0d060bcf321d3695ddc249e8f8069775bec62
• add a test for above linking
• DONE: https://lab.nexedi.com/nexedi/erp5/commit/fed0d060bcf321d3695ddc249e8f8069775bec62
• adapt alarm redrafting lines to use process_timeout if defined, use specialise link created
• DONE: https://lab.nexedi.com/nexedi/erp5/commit/f87f31b388c056136ecbb32055ace459c359844e
• wait for whole test suite to confirm no regression has been introduced
• Last test result with 4 unrelated failures
• ping back when done