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

erp5_catalog: Ignore case for title property and update default_erp5_catalog_id only when we create new erp5_catalog

erp5_catalog: Use searchFolder as list method as we have catalog objects as content which are ERP5 object

erp5_catalog: Install erp5_catalog_transition bt before erp5_catalog_storage as we need Catalog portal type early on

Earlier, migrateSQLCatalogToERP5Catalog was used only for creating a new ERP5Catalog
and then migrating the objects and properties from sql catalog to this new ERP5 catalog.
This sometimes led to the problem while we install new business templates which do have
Catalog methods. So, the soluton to this is to update this migration function to do the
updation part also. So now we can call this function everytime after we install a BT5
and it'll create/update ERP5Catalog as per needed.

Please note that this hack is not an efficient way to carry this process. Instead the
better option imho(Ayush) is to change completely the BT5 methods structure of handling
Catalog methods which at present time have hardcoded sql_catalog name attached to their
paths.