of Organisation_viewFinancialInformationList

In xhtml_style, just after clicking next or previous page in the listbox
buttons, the values selected in 'Section Category' and 'Section Category
Strict' were not used, because they were used from request and not from
as normal script parameters.

This fixes only the xhtml_style version, ERP5JS has another problem that
dialog fields values are reset when going to next page, so it would also
need this problem to be fixed.

Use correct portal type.

- Display the editor in ERP5 language, not browser language
 - Use PDF viewer for Drawing preview
 - Supports password protected PDFs
 - Others small changes

See merge request !1639

and several small fixes or changes to make this easier

See merge request nexedi/erp5!1642

This was a workaround for ChromeOS, but we realized it was not really good.
Disable it for the same reasons as nexedi/slapos!1196 :

 - not everybody use ChromeOS
 - this breaks the ctrl+click shortcut to go to definition/follow link
 - it makes ERP5 monaco editor behaves differently from others monaco editor
 - ChromeOS users can use chrome://flags/#use-search-click-for-right-click

When cleaning up Wendelin from restricted python pandas code
(see https://lab.nexedi.com/levin.zimmermann/wendelin/tree/remove-redundant-pandas),
it turned out that there was one line still missing in erp5.
This missing line caused a failed test in wendelin functional tests:

  https://erp5js.nexedi.net/#/test_result_module/20220614-1B46817BD/6

Readding the line fixed the test.

create_server returns either a BaseWSGIServer or a MultiSocketServer,
but add_task only exists in BaseWSGIServer - and the implementation is
simply [1]:

    def add_task(self, task):
        self.task_dispatcher.add_task(task)

by using self.task_dispatcher.add_task directly, we are compatible with
both cases.

This is relevant when running timerserver with runUnitTest, where we
create multiple sockets, one for http and one for web-dav.

1: https://github.com/Pylons/waitress/blob/v1.4.4/src/waitress/server.py#L290-L291

The default TestCase.__call__ collects errors in a test result that
was never retrieved, so errors were silently ignored.

By using TestCase.debug , we let errors propagate.

---

Minimal reproduction is running directly (ie. not with python -m unittest)
a script like this:

    import unittest

    class T(unittest.TestCase):
      def method(self):
        print('ah ?')
        boom
        print('oh')

    t = T("method")
    t()  # no error
    t.debug()  # NameError: name 'boom' is not defined

This helps debugging concurrency problems

This allows running tests using a timer server loop, that will invoke
process timer on all subscribers.
The need for this is to test a custom tool using timer server.

It was enough for 2 nodes, but with 4 nodes I sometimes saw errors.

This was a deprecated method that no longer exists since ZEO 4
https://github.com/zopefoundation/ZEO/commit/5423f110ddc1034ea0954495957894c60f6da78c

_setUpDummyMailHost is also used to prevent accidentally sending "real"
emails, so we also like to have it enabled for other nodes.

See merge request nexedi/erp5!1641

This happens in project related task report dialog (
testProjectRelatedTaskReport from
erp5_report_renderjs_ui_test:testFunctionalRJSReportLanguage )