Move CatalogKey, ColumnMetadata, ColumnMap, CatalogTable to dbt-common

[aranke]

Description

As per internal Slack conversation, we want to move the catalog artifact schema to dbt-common so adapters can depend on them (PR 1, PR 2).

This PR moves the following to dbt-common: CatalogKey, ColumnMetadata, ColumnMap, CatalogTable
Draft PR in dbt-core that keeps imports intact but uses code from dbt-common is here: dbt-labs/dbt-core#10253

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[github-actions]

Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 0% with 18 lines in your changes are missing coverage. Please review.

Project coverage is 64.04%. Comparing base (ddb28aa) to head (18fb414).

Files	Patch %	Lines
dbt_common/contracts/metadata.py	0.00%	18 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #147      +/-   ##
==========================================
- Coverage   64.39%   64.04%   -0.35%     
==========================================
  Files          51       51              
  Lines        3134     3151      +17     
==========================================
  Hits         2018     2018              
- Misses       1116     1133      +17     

Flag	Coverage Δ
unit	64.04% <0.00%> (-0.35%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.