When using `force_batch=true` with incremental models, it will fail if there is no data to write

[parsable-alex-antonison]

When using `force_batch=true` with incremental models, it will fail if there is no data to write

[nicor88]

Adding a bit more context.
The issue occur also for simple models like:

{{ config(
    materialized='incremental',
    incremental_strategy='merge',
    unique_key='user_id',
    table_type='iceberg',
   force_batch='true'
) }}

select 1 as user_id, 'a' as user_name

The issue seems to be in get_partition_batches and create_table_as_with_partitions

Here are some possible solutions:

• if the underlying dataset is empty - create_table_as_with_partitions can create an empty table from SQL - no hurt/no pain - it's possible to check if __tmp_not_partitioned is empty and if it's the case, we just create an empty relation as tmp table.
• if the user try to use force_batch with not partitioned tables -> we have 2 options:
  • all works normally and force_batch it's just ignored, e.g. pass partitioning(bool) to safe_create_table_as
  • we raise an error and ask the user to remove force_batch from not partitioned tables
• if the user works with partitioned tables by the data is not more than 100 partitions partition batches everything should still work. - must be tested

@svdimchenko FYI.