`meta` and `tags` should be `config`s under `columns:` (not properties)

[graciegoheen]

Housekeeping

• I am a maintainer of dbt-core

Short description

tags and meta are all being deprecated as properties and moved under config:

models:
  - name: <model_name>
    config:
      tags: ...
      meta: ...

we should do the same thing for tags and meta under columns: property with actual inheritance

Acceptance criteria

1. I can define tags and meta under new config: property under columns:

models:
  - name: <model_name>
    columns:
      - name: <column_name>
        config:
          tags: ...
          meta: ...

2. project -> model -> column inheritance should work the same way it does for tags and meta in other places

from our docs:

• tags are additive. If a model has some tags configured in dbt_project.yml, and more tags applied in its .sql file, the final set of tags will include all of them.
• meta dictionaries are merged (a more specific key-value pair replaces a less specific value with the same key)

3. deprecation warning for tags and meta under columns: as properties

[AlexanderStephenson]

Has this change been made for SourceDefinitions? We are using tags and meta for sources, and since last week we are now getting errors when running source freshness.

Encountered an error:
Compilation Error in operation data_common_dbt-on-run-end-0 (./dbt_project.yml)
'dbt.contracts.graph.nodes.SourceDefinition object' has no attribute 'alias'

[graciegoheen]

@AlexanderStephenson the changes were making for 1.10 will be backwards compatible - they will raise a deprecation warning (not a compilation error) for the legacy configuration pattern - more info here

Could you open up a bug report for the error you're encountering?

[MichelleArk]

closed by #11671

[FishtownBuildBot]

Opened a new issue in dbt-labs/docs.getdbt.com: dbt-labs/docs.getdbt.com#7357