dbt 1.10 compatibility with deprecated custom nodes

### Describe the feature
dbt announced deprecation of some node structures used in external tables, e.g. the expression node for columns or the ext_full_refresh node under the model (see https://docs.getdbt.com/docs/dbt-versions/core-upgrade/upgrading-to-v1.10#deprecation-warnings for details)

The new dbt vscode plugin using the fusion engine also lists these nodes as errors, as well as the dbt-autofix-tool

There's still time left until the end of 2025 to adapt, I just wanted to bring the topic up and ask if there are any plans on supporting the stricter dbt-structure.

### Describe alternatives you've considered
If we want to keep dbt-external-tables to create external tables from dbt 1.10 upwards, I don't see another option than adopting to the new structure and moving the custom-nodes to config- meta- nodes. Or the dbt-external-table-columns are included in the dbt-standard and aren't marked as errors (and autofixed)

### Additional context
This issue is not database specific, but only is relevant in upcoming dbt-versions

### Who will this benefit?
I think everyone updating dbt to the newer version would benefit from the compatibility