Enforce stricter naming in SQL/DDL

Multi-part identifiers in Teiid SQL have lax handling due to an early design decision to allow Teiid queries to mimic any naming/quoting used in a native query. The side effects of this is that '.' is not allowed in a column nor schema name, that quoting is effectively ignored - for example using a multi-part identifier in a DDL create does not scope to that schema:

create view "foo"."bar" ...

creates "foo.bar" in the current schema rather than bar in the foo schema.

We should at least introduce flags for strict handling and make sure ddl is compatible as possible.