The previous files were built on normal Linux
The updated files were built on SlapOS

We follow the standard jsmd format.

Ayush seems to submitted everything he got by compiling Pyodide.
Some of them are not needed for our erp5_notebook project. Remove it.

Support standard pyodide notebook grammar
Simply ignore the section "meta" and "plugin", support "%%code {"language" : "py"}"
instead "%% py"
We don't use pyodide.js anymore
erp5_notebook: Add iodide.output
Display the JS code reuslt if there have

To use variation is still too complex.

MatrixBox is often used for price tables or code tables. So it is always useful for end users to display its contents.

Make it available for ERP5JS

Store a new Selection everytime a Listbox content is calculated.
This will allow actions checking the selection params to get expected results.

Propagate selection_name in dialog if the dialog doesn't contain a listbox itself.

erp5 jio gadget: follow jio 3.38.1 changes

Ensure that if the web site policy is just set to Must-Revalidate, all documents are updated.
It forces HTTP Cache middleware to refresh their contents.

See nexedi/erp5@f402de4e

Because the number of objects to be retrieved can be too big, or because the query can be complex (depending on the definition of the domain), and because searchAndActivate add a sort on uid (even if it's a primary key, this sort is amplified by the 2 previous reasons), searchAndActivate should be activated to avoid timeouts for the user

erp5_simulation_fast_input: Solve Divergences dialog: Display all divergences in a single ListBox page.

This dialog and its JS gadget does not handle multiple pages ListBox (because
gadget_solve_divergence_dialog.js assumes that the view is the last part of
the URL) and this is not actually needed (customer seldom goes over the
previous limit to 20 anyway).

How to reproduce:
  1. Create >20 divergences (20 lines per page used to be displayed).
  2. Go to Solve Divergences dialog:
     => gadget_solve_divergence_dialog.js:
        -> location.pathname == /erp5/purchase_order_module/42/Delivery_solveDivergenceAction.
           -> basedir=/erp5/purchase_order_module/42.
              => /erp5/purchase_order_module/42/Delivery_getSolveDivergenceDialogParameterFormBox XHR'ed: OK.
  3. Go to any other ListBox page:
     => gadget_solve_divergence_dialog.js:
        -> location.pathname == /erp5/purchase_order_module/42.
           -> basedir=/erp5/purchase_order_module.
              =>/erp5/purchase_order_module/Delivery_getSolveDivergenceDialogParameterFormBox XHR'ed: NOK:
                 [...]
                   Module script, line 4, in Delivery_getSolveDivergenceDialogParameterFormBox
                     - <PythonScript at /erp5/Delivery_getSolveDivergenceDialogParameterFormBox used for /erp5/purchase_order_module>
                     - Line 4
                     solver_process = context.getSolverValueList()[-1]
                 AttributeError: getSolverValueList

erp5_simulation_fast_input: Solve Divergences dialog: Handle error when XHR'ing Solver configuration fails.

When user clicks on the radio button to Accept Decision for example,
Delivery_getSolveDivergenceDialogParameterFormBox is called (XHR) and when it
failed, the 'Solve Divergences' button was disappearing and nothing was
displayed to end-user.