Support dialect declaration for SQL composition #18

[Brayden]

Is your feature request related to a problem? Please describe.
When the query builder is composing a runnable SQL statement, it will become imperative for the dialect of the destination engine to be known so we construct valid SQL statements.

Describe the solution you'd like
By default, a dialect can be set by the initial Connection object. For example if you declare to use the Neon connection object, it could preset the dialect to "postgres"

You can explicitly set a dialect yourself.

const db = Outerbase(neon);
db.dialect = "postgres"

Support the following dialects:

type SQLDialect = "postgres" | "mysql" | "sqlite" | "mssql" | "sqlserver" | "oracle" | "mariadb";

Describe alternatives you've considered
TBD

Additional context
TBD

[Brayden]

An example of some differences between db engines/dialects include, but not limited to:

• Data types
• Object handling (JSON & Arrays)
• Escaping
• RETURNING isn't supported on all database engines