erp5_data_notebook bt5: Use dictionary to save module imports instead of saving it as list of strings.

Using dictinary its easier to update modules frequently.

For example, executing code:

'''
import numpy as np
import numpy
'''

would result as :
local_variable_dict['imports'] = {'numpy': 'numpy', 'np': 'numpy'}
which is what we expect to be saved in globals() also.

Problem: Module objects are not picklable, thus, trying them to save in
local_variable_dict which is further saved in ZODB via ActiveResult object
of CMFActivity was giving error. So, its better to save the module objects
as code_strings in local_variable_dict.

As for now, for example:
local_variable_dict = {'imports': ['import numpy as np', 'import matplotlib as mpl'],
			 'variables': {'a':1, 'b:2'}}
for jupyter_code = """
import numpy as np
import matplotlib as mlp
a= 1; b=2; print a+b
"""

erp5_data_notebook bt5: Update Listbox containing Data Notebook Lines to maximum of 20 lines per page

erp5_data_notebook bt5: Refactor test to use reference while searching through portal_catalog instead of notebook_code which was incorrect as there was no key as such in SQL_catalog for erp5

erp5_data_notebook bt5: Make notebook_code and notebook_code_result field uneditable for Data Notebook Line object

erp5_data_notebook bt5: Changed name of portal type from Data Notebook Message to Data Notebook Line and changes in various scripts where it has been used

erp5_data_notebook bt5: Rename Notebook Cell Input and Notebook Cell Output in Data Notebook Message

erp5_data_notebook bt5: Use interactivity/mode and finally execute all code using exec to get rid of try:except

erp5-data-notebook bt5: Refactor testExecuteJupyter to new JupyterCompile where we are letting errors fails loudly in erp5

erp5-data-notebook bt5: Remove exception catching from Base_runJupyter external function and let the errors be raised loudly

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