erp5_data_notebook bt5: Add transaction abort and fail loudly in case of error in transaction script

erp5_data_notebook: Check user permission for at entry point for Base_executeJupyter python script so that non-developer user cannot execute python code through script

erp5_data_notebook: Refactor jupyter_compile to only return the local variables which are added after code execution

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