resolve redundancy of column keys from dbt yaml

[dataders]

related: https://github.com/dbt-labs/internal-analytics/pull/3992

preview.94 (docs) is now conformant with dbt Core in that:

• if there is model with duplicate column keys
• only the last definition will be used

accordingly, there's parse will throw a warning when this is the case like the below.

warning: dbt1033: Column 'initial_catch_up_date' is defined multiple times in 'models/staging/googlesheets/stg_googlesheets__rev_schedule_overrides.sql'. Only the last definition will be used.

dbt-autofix should fix this where possible.

one catch that might make this a 'manual fix'

how to automatically pick which column config is the correct one?