ERP5 SQL Methods would be the next step in shifting from Zope base catalog
to ERP5 Catalog. ZSQLMethods are used extensively inside the catalog,
so the better option would be to make an ERP5 object for them.

This change solves the error which one gets while trying to access properties
Form for an ERP5 object having one or more of its property of type 'selection'
or 'multiple selection'.
For example: If you try to access property form for any portal_type objects,
you'll get an error : 'select_variable' is not defined. This is because of the
absence of the property select variable for the property of type multiple selection
which in case of portal_type object is property sheet list.

This is helpful for ERP5 views/forms which displays selection or multiple selection
type object.

erp5_catalog: Add list suffix for lines type property in portal skins for Catalog_viewMethodList view

erp5_catalog: Use setProperty from Base class instead of _updateProperty from PropertyManager to update/set property for ERP5Catalog object

erp5_catalog_transition: Add select_variable property in standard property in Catalog property sheets

Now as CatalogTool is a ERP5 object(BaseTool), we need CatalogTool.getPath
to direct to getPath function from Base class, so the best way was to change
the tests where it relied on CatalogTool.getPath to call getpath from ZSQLCatalog.

erp5_catalog: Revert back to monkeypatch getPath with getpath in ZSQLCatalog and solve inhertiance conflict for CatalogTool

erp5_catalog: Update select_variable and type for Catalog and CatalogTool property_sheets objects respectively

erp5_catalog: Makes better sense to have bt5 in bootstrap as it'd be installed during ERP5Site setup