feat(athena): Part 3 — accept partitioned_by, table_properties and force_batch as model configs

[aoelvp94]

Part of #16252. Related: #13822. Independent PR; the sequence is at the bottom.

Problem

WarehouseSpecificNodeConfig has no Athena keys. On a real project dbt parse reports every dbt-athena model config as UnusedConfigKey (partitioned_by x27, table_properties, force_batch) and every +table_properties block in dbt_project.yml as a SerializationError ("Custom keys must go under +meta"). 35 errors on a 750-model project, all this one class.

Solution

Adds every Athena model config the vendored macros read through config.get(...), following the existing per-warehouse pattern: struct field in common.rs; the _eq binding, && chain and named tuple in same_warehouse_config; the +key twin in ProjectModelConfig with its is_some(); the two conversions in model_config.rs; and the five exhaustive struct literals (source_config.rs, unit_test_config.rs, seed_config.rs, snapshot_config.rs, data_test_config.rs).

26 keys in total. partitioned_by, table_properties and force_batch are the three dbt parse flagged; the other 23 are bucket_count, bucketed_by, delete_condition, external_location, field_delimiter, ha, insert_condition, lf_grants, lf_inherited_tags, lf_tags_config, merge_update_columns_default_rule, merge_update_columns_rules, native_drop, partitions_limit, s3_data_dir, s3_data_naming, s3_tmp_table_dir, seed_by_insert, seed_s3_upload_args, temp_schema, update_condition, versions_to_keep, write_compression. Each is a hard error (UnusedConfigKey) when a model sets it, not a warning. format, unique_tmp_table_suffix and table_type are already declared for other adapters with the types Athena needs.

Note for reviewers: the compiler enforces the five struct literals but not the _eq bindings and the && chain. A key added to WarehouseSpecificNodeConfig and missed there compiles and silently makes state:modified blind to that config, so the test added here sets each of the 26 keys in turn and asserts same_warehouse_config notices.

Verification

• cargo fmt --check, cargo clippy -p dbt-schemas --all-targets --all-features and cargo nextest run -p dbt-schemas (673 passed) clean on the pinned toolchain, including the new athena_model_configs_are_compared guard test.
• dbt parse on the 750-model project: 35 errors to 0.

Feedback wanted: whether declaring each key individually is the shape you want here, or whether an adapter-owned passthrough would suit a config surface this wide.

Sequence (independent PRs, each compiles alone against main)

• Part 0: feat(athena): Part 0 — map Backend::Athena to its driver entrypoint and send the driver's output-location option #16365 — ADBC driver wiring
• Part 1: feat(athena): AthenaDbConfig profile schema #16274 — AthenaDbConfig profile schema (@fpiped)
• Part 2: feat(athena): Part 2 — fill the parse-path todo!() arms and the config alias #16367 — dbt-adapter core wiring
• Part 3: this PR — model config keys
• Part 4: feat(athena): Part 4 — vendor the dbt-athena 1.11.0 macro package #16369 — dbt-athena macro package
• Part 5: feat(athena): Part 5 — AthenaMetadataAdapter and athena_get_relation #16374 — AthenaMetadataAdapter and get_relation
• Parts 6+7: branch ready, not yet opened — Glue / Lake Formation housekeeping shims and the table / incremental helpers (athena/parts-6-7-execution); see also feat(athena): Part 6 — AthenaAdapter methods behind the dbt-athena macros #16376
• Part 8: feat(athena): Part 8 — run dbt unit tests on Athena #16370 — dbt unit tests on Athena
• Part 9: feat(athena): Part 9 — dbt init profile wizard for Athena #16375 — dbt init profile wizard
• Full branch for context: https://github.com/aoelvp94/dbt/tree/spike/athena-profile-parse

Checklist

• I have read the contributing guide and understand what's expected of me.
• I have run this code in development, and it appears to resolve the stated issue.
• This PR includes tests, or tests are not required or relevant for this PR.
• This PR has no interface changes (config schema gains keys that were previously rejected).

[fpiped]

Tested with the stack: model configs the dbt-athena macros read are hard errors when set on a model (UnusedConfigKey), because only partitioned_by, table_properties and force_batch are declared. Hit in practice: ha and s3_data_naming. The full set of Athena-specific keys the macros config.get(...): bucket_count, bucketed_by, delete_condition, external_location, field_delimiter, format, ha, insert_condition, lf_grants, lf_inherited_tags, lf_tags_config, merge_update_columns_default_rule, merge_update_columns_rules, native_drop, partitions_limit, s3_data_dir, s3_data_naming, s3_tmp_table_dir, seed_by_insert, seed_s3_upload_args, temp_schema, unique_tmp_table_suffix, update_condition, versions_to_keep, write_compression (plus partitioned_by, table_properties, force_batch, table_type, which already pass).