Move from SQLCatalog to ERP5Catalog as the default Catalog inside ERP5.
The major difference is use of Products.ERP5Type.Core.Folder as Catalog
base class.

Significant addition/changes in
-------------------------------

  ERP5Catalog class:
    Inherit from Catalog class from Products.ZSQLCatalog.SQLCatalog instead of copy-pasting the whole code again.
    Monkey patch some property setters and getters to maintain consistency
    Override getCatalogMethodIds cause it uses global variable in SQLCatalog.Catalog
    Add FilterDict and Filter class to have consistency with `filter_dict` attribute of SQLCatalog

  BusinessTemplate:
    Update BusinessTemplate installation with updated filter_dict
    Also, use dynamic migration while installing the catalog method objects for
    bt5. This way we have SQL Methods migrated just after installation.

  Tests:
    Update tests according to changes in portal_catalog

  SQLCatalog, testZSQLCatalog:
    Cleanup for unusable functions

Create the SQLMethod class based on ZSQLMethods.SQL
class and XMLObject.

inotifyx is has no support for Python 3 and
it does not seem to be maintained anymore.

/reviewed-on nexedi/erp5!484

The erp5 site creation fails due to a dependency error. Dependency to erp5_full_text_myisam_catalog was added to the erp5_scalability_test business template.

/reviewed-on nexedi/erp5!483

fast synchro is not ready.

Allow to overwrite this inside project to init Properties like reference.

Because it is mainly used from the 'initsite' zope.conf section, the passed
value is often a string, hence the automatic cast to integer.

The default is defined in erp5_core: 1
The specific value '0' disables storage in ZODB.
Another other value sets the interval.

- Use unrestricted _edit method on reportTaskStatus - restrictedTraverse applies security anyway
- Remove some useless code
- Fix TypeError: stopUnitTest() takes exactly 3 arguments (4 given)

In order to use setting in multiple application on same domain.

/reviewed-on nexedi/erp5!474

createTestResult is called also without node_title, and it shall allow
execution in such case.

Such parameter can produce undesired conditions
(ex: FROM catalog as node, ... WHERE node.uid > 0 AND ...) causing poor
performance. So avoid introducing this parameter when its value is empty.

There is no need for any client to call tool directly.

This results with calling correct methods on the server.

This results with calling correct methods on the server.

The module is to access Distributor not the whole tool.

This results with calling correct methods on the server.

Since distributor is used, tests need adaptation:

 * created default Test Node and Test Suite, required by
   Distributor.createTestResult
 * adapted _createTestResult to reuse created documents
 * adapted some tests in order to reuse created documents