Prevent random failures when email table is not present

The main reason for the test_installBusinessTemplatesFromRepository_update_catalog
test is assert if the activities from created from clear catalog are
present on the activity lists or not.

This change re-creates the table using zsqls introduced by
erp5_ingestion_mysql_innodb_catalog to make sure the table is there when
the index activites related to the new BT5 be launched.

product/ERP5/tests/testTemplateTool.py

@@ -499,6 +499,11 @@ class TestTemplateTool(ERP5TypeTestCase):
       self.assertNotEquals(bt.getId(), None)
       self.commit()
       self.checkFolderReindexAllActivityNotPresent()
+      # Before launch activities make sure email table is created even
+      # catalog is not created.
+      catalog_tool = self.portal.portal_catalog
+      catalog_tool.erp5_mysql_innodb.z0_drop_email()
+      catalog_tool.erp5_mysql_innodb.z_create_email()
       self.tic()
 
       bt5_name = 'erp5_odt_style'