Add Databricks handler for get_table_types_sql.sql

[Harmuth94]

resolves #768

This is a:

• documentation update
• bug fix with no breaking changes
• new functionality
• a breaking change

All pull requests from community contributors should target the main branch (default).

Description & motivation

get_relations_by_pattern throws an error when using the databricks adapter on schemas in a Unity catalog. The error comes from the table having the table_type MANAGED in the information_schema.tables table.
Adding a handler for databricks allows the macro to as expected with data in a Unity catalog.

Checklist

• This code is associated with an Issue which has been triaged and accepted for development.
• I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)
  • BigQuery
  • Postgres
  • Redshift
  • Snowflake
  • Databricks
• I followed guidelines to ensure that my changes will work on "non-core" adapters by:
  • dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
  • using the limit_zero() macro in place of the literal string: limit 0
  • using dbt.type_* macros instead of explicit datatypes (e.g. dbt.type_timestamp() instead of TIMESTAMP
• I have updated the README.md (if applicable)
• I have added tests & descriptions to my models (and macros if applicable)
• I have added an entry to CHANGELOG.md

[Harmuth94]

Tests for Redshift and bigquery are failing but the proposed change does not affect them in any way.

[joellabes]

Amazing! Thanks @Harmuth94 🤩 sorry for the delay in getting back to you!