erp5_catalog: No need to add Catalog Tool via the earlier manage_addProduct as it is an ERP5 object now

This was needed because of the problem being faced while debugging,
so maybe when we finally migrate, we need to remove/modify this
function.

Imho, the better way would be to migrate everything(Catalog, SQLMethod,
PythonScripts) all in one go instead of separately doing this.

Changes and addtions :
	- Separate view for contents and properties for Catalog object in ERP5.
	- Separate view for advanced properties and template body for SQL Method objects in ERP5.
	- Updated URL columns for contents listbox of Catalog object.

erp5_catalog: Modify mistake with dtml file path and remove initialization of XMLObject and ZSQL in SQLMethod __init__

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