Teiid importer needs to handle schema and catalog cases for generated model

When importing via the Teiid Importer, an example of Teiid DDL for tables:

CREATE FOREIGN TABLE "accounts.ACCOUNT" (
COL1 long NOT NULL DEFAULT '0' OPTIONS (..., NAMEINSOURCE '`ACCOUNT_ID`', ...),
) OPTIONS (..., NAMEINSOURCE '`accounts`.`ACCOUNT`', ...);

Since some dbs support catalogs, the 'dotted' names can be multiple levels deep. We need to use a combination of NameInSource and potentially filtering on the DDL retrieval to determine how the model entities are to be created.