[CT-3267] [Feature] Debug log when type_code fails to convert to a data_type

[dbeatty10]

resolves #38

Problem

Postgres allows user defined data types. It also has some non-standard data types like money, uuid, etc. If dbt doesn't recognize the data type, dbt doesn't completely fail, but it also doesn't explain what's going on.

Solution

Uses dbt-labs/dbt-adapters#135 to emit a debug-level log message any time a data type is not recognized within dbt-postgres. That way, users can at least see in the logs what is going on.

Log messages will look like the following:

The type_code 790 was not recognized

Checklist

• I have read the contributing guide and understand what's expected of me
• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests
• This PR has already received feedback and approval from Product or DX

[mikealfare]

Looks good, just remember to revert the dependencies to point to main.

[mikealfare]

I think this is going to be easier to merge post the pre-commit merge, so I'd like to get that in first and then rebase this PR. I added it to my sprint backlog for this sprint so I don't lose track of it.