With nexedi/wendelin@3f887532 and nexedi/wendelin@b4c22280 we already removed numpy security duplications:
this code already exists in ERP5 (with nexedi/erp5@a254bf50).
But we still missed some code parts: https://lab.nexedi.com/nexedi/wendelin/blob/b4c222803027a2d0d0fae793a4f16d4bea85f87d/product/Wendelin/__init__.py#L49-52
(perhaps because they looked different between erp5 and wendelin).

Furthermore with nexedi/erp5@79fa584e the last
numpy parts which only existed in Wendelin were also migrated to ERP5,
which is why we can finally also remove this from Wendelin.

Now all numpy related RestrictedPython definitions can be found in
the ERP5 codebase and they are no longer distributed over both ERP5
and Wendelin.

/tested-at https://erp5js.nexedi.net/#/test_result_module/20230305-F68A7FFE

self.publish() had a bug regarding status code for empty responses on
Zope2 and that bug was fixed in Zope4, this adjust the code to support
both versions.

this is already done in ERP5

Base_wendelinTextToNumpy just takes a string and pass it to numpy.load,
but numpy.load will load pickles (problem from https://github.com/numpy/numpy/issues/12759 ).
Therefore we disallow loading pickles here until this becomes the
default in newer numpy versions.
Co-authored-by: Jérome Perrin <jerome@nexedi.com>

   All modules should use this base category.

With nexedi/erp5@a254bf50 numpy
was allowed in erp5 upstream Restricted.py. There is no need for any
duplication in wendelin.

Tested at: https://erp5js.nexedi.net/#/test_result_module/20230223-AE5B8F75

erp5_wendelin_data_lake_ingestion_default_security_model: those module's Business Application are big data

See merge request nexedi/wendelin!106

Relicense to GPLv3+ with wide exception for all Free Software / Open Source projects + Business options.

See merge request nexedi/wendelin!105

Relicense to GPLv3+ with wide exception for all Free Software / Open Source projects + Business options.

Nexedi stack is licensed under Free Software licenses with various exceptions
that cover three business cases:

- Free Software
- Proprietary Software
- Rebranding

As long as one intends to develop Free Software based on Nexedi stack, no
license cost is involved. Developing proprietary software based on Nexedi stack
may require a proprietary exception license. Rebranding Nexedi stack is
prohibited unless rebranding license is acquired.

Through this licensing approach, Nexedi expects to encourage Free Software
development without restrictions and at the same time create a framework for
proprietary software to contribute to the long term sustainability of the
Nexedi stack.

Please see https://www.nexedi.com/licensing for details, rationale and options.

53b0c240 split categories to a separate bt5 which we need to install.

See merge request nexedi/wendelin!104

same as others