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

[dbeatty10]

Is this your first time submitting a feature request?

• I have read the expectations for open source contributors
• I have searched the existing issues, and I could not find an existing issue for this feature
• I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Originally posted by @rlh1994

Would it be useful to add a debug level warning when it fails to find a type? In particular if someone is using the column.Data_type from a get_column_schema_from_query call it might not be obvious why something is failing without directly outputting all the column data types?

Originally posted by @dbeatty10

@MichelleArk how would you feel about adding this ☝️ debug output when the type_code isn't found?

Originally posted by @MichelleArk

It may be a little redundant given unknown type_code will appear in the error message either way. So I'd either omit it or write a more informative message like"type_code not found in adapter-provided lookup, defaulting to 'unknown type_code'"

And we may actually need to use fire_event to fire a debuglevel event as opposed not logger.debug

The log level could be a warning rather than debug if we choose.

Describe alternatives you've considered

A couple alternatives to fire_event:

1. logger.debug
2. No logging at all

Who will this benefit?

The beneficiaries are similar to dbt-labs/dbt-core#8900. The primary intended audience is folks directly using get_column_schema_from_query (like described in dbt-labs/dbt-core#8877) that might not realize a translation wasn't possible.

Are you interested in contributing this feature?

PR for consideration: dbt-labs/dbt-core#8957

Anything else?

No response