erp5_data_notebook: Add dict to convert string to Boolean in Base_executeJupyter python script for getting all the data notebooks

erp5_data_notebook bt5: Updated extension JupyterCompile to use globals variable while running exec command

This BT is used to interact ERP5 with Jupyter and execute the python code.
1. External method `Base_executeJupyter` to interact between code from Jupyter and ERP5 backend.
2. Module - Data Notebooks
3. Unittest `JupyterCompile` to test external method and extensions.

This will drop any query containing only some space characters

This helps to navegate quicker among the documents.

This is achieved by passing 'undefined' value in the option dict.
Example: {page: undefined, form: 'view'}

[erp5_web_renderjs_ui] Ensure that relation field jump link does not allow pagination on random documents

Each worklist links to the module view of the first matching portal_type.
A search query is provided to filter the documents matching the worklist.

This allow to provide worklist information to a javascript application.
allDocs query parameter are provided to get list of document to work on.

Include a new Distributor, Test Suite and also Unit Test related class to Handle SlapOS Test Agent kind of tests.

local_roles can not be expressed as a catalog query and should be provided as an explicit value

[erp5_web_renderjs_ui_test] Sort document before paginating to not depend of catalog random ordering

And remove trailing whitespaces

Try to rely on listbox content instead

When using erp5_deferred_style, each report section is rendered in an
independant request, so test should not create a situtation where request form
is same for all report section, because request form parameters become
selection parameters.

This new property will not be available until we upgrade
erp5_property_sheets, so we have to use a backword compatible accessor.

Improve default dialog by avoiding doing "update" action to see solver parameters. Instead,
use javascript to automatically fill the "parameter" column when a solver is selected. Since there
is not yet good solution to have this in both legacy user interface and new interface, use a
separated business template instead of just changing the original dialog.

Use a lot proxification to avoid duplicatation of configuration.