Term is "Support Request Type".

The term is "Support Request Type" so use it consistently in every place, instead
of mixing "Type" or "Support Type".

Since c4026c75 (erp5_officejs: change Notebook app editor from
iodide_master to gadget_jsmd_eval, 2020-09-23), erp5_officejs depends on
erp5_notebook, but erp5_notebook is not present in erp5 repository, it is
in erp5-bin repository.

This test works by taking an old Data.fs and running upgrader, to update
to latest code. The first thing it does is using
setupAutomaticBusinessTemplateRepository to discover folder containing
business templates repositories and enabling them. Until now it was doing
only for erp5_core (to find parts/erp5/product/ERP5/bootstrap) and for
erp5_base (to find parts/erp5/bt5/). Now we also need to do that for
erp5_notebook, to find parts/erp5-bin/bt5/

Use reveal 3.9.2
Remove font not present from reveal theme.

See ee81e26e (comment 121758)

See ee81e26e (comment 121757)

that would return the whole catalog

Only basic fields are supported (no gadgetfield for now).

See merge request nexedi/erp5!1275

- this action relies on paged.js library for pagination

Don't log and fix a few resource warnings

See merge request nexedi/erp5!1307

Add missing field, used in testFloatFieldStep

It follows commit ce233f79

Some fields may use div element without expecting 100% width.
Example: formbox and diff gadget.

this prevents ResourceWarnings on python3

this prevent ResourceWarnings on python3

this is way to verbose and not really useful

Why invent a different way, making it harder to consistently patch
validated_hook ?

For example, allows upgrading a Business Template when an ERP5 Form is
replaced by a PythonScript in a skin folder.

When running on testnode, runUniTest is responsible for picking a free $DISPLAY.
This is implemented by starting Xvfb on a $DISPLAY, waiting a bit and if it is
still running we assume the $DISPLAY was free. But it seems sometimes we don't
wait enough, when testnodes are overloaded.

This implementation is wrong, we could run a command check that X is running,
but as explained in the code command below, xdpyinfo or other tools are
currently not available in test environment. Since we are considering switching
this to seleniumserver (which would take care of running a X Server for us) so
this is OK for now.