Attributes moving / exclusively available within `config` for Fusion

### Contributions

- [x] I have read the contribution docs, and understand what's expected of me.

### Link to the page on docs.getdbt.com requiring updates

https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-fusion

### What part(s) of the page would you like to see updated?

Previously duplicated properties that were present as **both** top-level keys and nested within config are now exclusively nested within config. This has implications for:
- getting these attributes out of `{{ graph }}`
- parsing these attributes from `manifest.json`

This also includes `column`-level attributes, `tags` and `meta`:
```sql
-- before: {{ model['columns']['id']['meta'] }}
-- after: {{ model['columns']['id']['config']['meta'] }}
```

### Additional information

- https://github.com/dbt-labs/dbt-autofix/issues/46

This change is:
- _required_ for Fusion
- _supported_ in dbt Core v1.9+ (with back-compat for previous syntax)