[FEATURE] Robustly Support ODBC Connection

[TheCedarPrince]

As of right now, ODBC support via ODBC.jl is perfunctory at best within DBConnector. It is not clear to me how much to offload to a user of an ODBC connection or if we should automatically install and set-up ODBC connections. Due to the variation of ODBC drivers, it seems like the most logical step is to require users to set up ODBC connections themselves. @quinnj , would you be able to comment on this approach overall?

Additionally, the way that I understand ODBC.jl is that ideally a _dbconnect dispatch should support the following functionality:

1. Allow a user to either give a path to an ODBC driver or have DBConnector perhaps choose the most logical driver
2. Allow the user to specify the type of dbms they are using so as to potentially anticipate inconsistency between ODBC drivers
3. Enable users to pass in any count of kwargs
4. Construct connection string for that specific DBMS instance via their respective ODBC driver
5. Create a DBInterface.Connection successfully

I feel like there may be other sorts of functionality that will need to be created in the future specific to a particular DBMS instance such that we will create file structures like src/odbc/odbc_sql_server.jl or something to that effect. But that may be overcomplicating things.

Either way, I am open to ideas, suggestions, and thoughts here.