Add ZODB Document BusinessTemplate tests as expected failure for Constraint and Test (not implemented yet).

This fixes filesystem Document-related tests in testBusinessTemplate.

Otherwise, following ZODB Document tests will fail because of the ZODB
Document created but not removed in that test.

Before, ConsistencyMessage were stored into a separate workflow variable,
instead of using error_message workflow variable which contains instances of
Message.

The only purpose of having Interaction Workflow defined on ComponentTool
_setObject and _delObject was for BusinessTemplate installation and
uninstallation, however the reset was also triggered when a new draft
Component was being added. Instead, perform the reset in BusinessTemplate
DocumentTemplateItem.

This new Role is defined only on portal_components and users can be only added
to this Role through editing zope.conf. Also, add a Permission for reset as
this role is not available outside of portal_components and is still useful
for Workflows for example.

Also, Rename *MigrateAllComponentFromFilesystem to *MigrateSourceCodeFromFilesystem.

This avoids having two interaction workflow for resetting dynamic classes and modules.

Instead, use savepoint which avoids triggering interaction workflows.

Also, set _archive properly for ZODB Document and Extension.

Add missing version in Component document_id for testBusinessTemplate (087ef32b908c9b384f5769fa2375c3202eff2ed5).

This reverts commit deb7e37e7690d50a6dc1e9aab05f4a7099973287 which introduced
a regression (test_BusinessTemplateWithDocumentPropertySheetMigrated failed).

Conflicts:

	product/ERP5/Document/BusinessTemplate.py

These tests also check whether recordable properties are properly set and cleared.

Checking the validation state is not enough as the validated value (save
through RecordablePropertyMixin) should never be overriden even when a
Component in modified state is saved and still contain errors.