feat(athena): add disable_batch_fallback config option

[dtaniwaki]

Summary

• Add disable_batch_fallback config option (default False) to dbt-athena
• When set to True, TOO_MANY_OPEN_PARTITIONS errors are raised instead of silently falling back to batch insert mode
• Applies to both table and incremental materializations (CTAS, insert, and iceberg merge)

Motivation

Currently, dbt-athena automatically falls back to batch mode when Athena returns TOO_MANY_OPEN_PARTITIONS on partitioned tables. This is convenient but can mask issues silently. The new disable_batch_fallback option gives users explicit control to fail fast when this error occurs.

Usage

-- table materialization with partitions
{{ config(
    materialized='table',
    partitioned_by=['date_column'],
    disable_batch_fallback=true
) }}

-- incremental materialization with partitions
{{ config(
    materialized='incremental',
    partitioned_by=['date_column'],
    disable_batch_fallback=true
) }}

Note: TOO_MANY_OPEN_PARTITIONS only occurs on partitioned tables. This config has no effect on non-partitioned tables.

Test plan

• Unit tests for run_query_with_partitions_limit_catching with disable_batch_fallback=True and False
• Unit test for non-partition errors always raising regardless of config
• Pre-commit lint (black, flake8, mypy) passes