This is needed for synchronisation with a file system. Then we need to address
each bucket by key (e.g. filename). But we also need to address by the order of
ingestion for processing with progress indicator.

/reviewed-on nexedi/wendelin!29

Commit transaction so for next test run we are sure that data_stream has no data and it doesn't affect test execution.

created thus it is needed to wait for server side activities to be
processed

Conflicts:
	bt5/erp5_wendelin/DocumentTemplateItem/portal_components/document.erp5.IngestionPolicy.py
	bt5/erp5_wendelin/TestTemplateItem/portal_components/test.erp5.testWendelin.py

For backward compatibility with ingestion policy scripts, the message body is
turned into a 'data_chunk' request parameter.

By not having anymore to convert to/from application/x-www-form-urlencoded,
this fixes a severe performance issue, in particular when ingesting a lot of
data with fluentd (Ruby uses regex to convert).

/reviewed-on nexedi/wendelin!28

Data ingestion batch does not have validation workflow, so
we cannot validate it.

Ingestion operations which write to data stream do not
have bucket_reference parameter. Now we do only pass
this parameter if we get it from the tag parsing script.

Transformation at append of data to Data Stream is triggered by an activity not at append time any more thus test is redundant.

erp5!339

Conflicts:
	bt5/erp5_wendelin/DocumentTemplateItem/portal_components/document.erp5.DataArray.py
	bt5/erp5_wendelin/DocumentTemplateItem/portal_components/document.erp5.DataArray.xml
	bt5/erp5_wendelin/DocumentTemplateItem/portal_components/document.erp5.DataBucketStream.py
	bt5/erp5_wendelin/DocumentTemplateItem/portal_components/document.erp5.DataBucketStream.xml
	bt5/erp5_wendelin/PortalTypePropertySheetTemplateItem/property_sheet_list.xml
	bt5/erp5_wendelin/bt/template_action_path_list
	bt5/erp5_wendelin/bt/template_portal_type_id_list
	bt5/erp5_wendelin/bt/template_portal_type_property_sheet_list

/reviewed-on klaus/wendelin!6

/reviewed-on nexedi/wendelin!25