categories. This is usually needed for Wendelin applications where for some
reasons data is stored in different Data Streams which must form a logical and sorted "link".
Add test.

See merge request nexedi/wendelin!42

See merge request !41

Allow owner of a Data Stream to edit it despite published. In normal ERP5 this is not normal but with Data Lake functionality validation is done at ebulk side (which also takes care of increasing automatically Data Set's version). This is quite simplified model of ebulk only validation of a Data Set but sufficient for most cases.

Rename validation_workflow (which duplicates erp5_core's one.) to data_validation_workflow which ash one new state only 'Published'
Cleanup worklists.

This reverts commit ab6250a1.

Validates state's meaning is that it has passed a validation by content - either ebulk client side or Wendelin side. It's not meant to be part of publication context.

Make it possible to configure if default (open) security model is to be installed for Wendelin's Data Lake. Default is not install.

Add new states for Data Stream and Data Set so we can have a more complex security models (based on DMS' publication_workflow).