Pass dynamic filter predicate to ConnectorSplitSource#getNextBatch

[chenjian2664]

Description

Move dynamic filter waiting logic from individual connectors into the engine layer by adding a TupleDomain<ColumnHandle> dynamicFilterPredicate parameter to ConnectorSplitSource#getNextBatch, so connectors receive the resolved predicate per batch without needing to hold a DynamicFilter and manage wait/timeout logic themselves.

Previously, IcebergSplitSource (and DeltaLakeSplitSource) each duplicated the same pattern: hold a DynamicFilter, poll isAwaitable()/isBlocked(), manage a Stopwatch against a connector-specific timeout, and only then call into Iceberg's planning API. This logic now lives entirely in ConnectorAwareSplitSource, which waits for dynamic filter completion (controlled by a new dynamic_filtering_wait_timeout system session property backed by DynamicFilterConfig) and passes dynamicFilter.getCurrentPredicate() to the connector on each batch call.

The change is split into two commits:

1. Engine/SPI: Add getNextBatch(int, TupleDomain<ColumnHandle>) as the new primary method (default delegates to the deprecated getNextBatch(int)); move wait/timeout ownership into ConnectorAwareSplitSource; update ClassLoaderSafeConnectorSplitSource to forward the predicate.
2. Iceberg: Override the new method in IcebergSplitSource; remove DynamicFilter/Stopwatch fields; remove iceberg.dynamic-filtering.wait-timeout config property (marked @DefunctConfig) and the dynamic_filtering_wait_timeout connector session property; update tests and docs.

Additional Changes

• Connectors that still override the deprecated getNextBatch(int) continue to work via the default bridge — no changes required in other connectors.
• BaseIcebergConnectorTest and TestIcebergDynamicPartitionPruningTest updated to set the engine-level dynamic_filtering_wait_timeout system property instead of the removed Iceberg-specific one.

Additional context and related issues

Release notes

() This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
(x) Release notes are required, with the following suggested text:

  ## SPI                                                                                                                                                                                                                               
  * Pass the resolved dynamic filter predicate to connectors per batch. ({issue}`29206`)                                                                                                                                                                                                                                                                                                           
                                                                                                                                                                                                                                       
  ## Iceberg connector                                                                                                                                                                                                                 
  * {{breaking}} Remove `iceberg.dynamic-filtering.wait-timeout` configuration property.                                                                                                                                                            
    Use the engine-level `dynamic-filtering.wait-timeout` instead. ({issue}`29206`)

[ebyhr]

Could you rebase on master to resolve conflicts?

[ebyhr]

I hope @raunaqmorarka chimes in this PR.

[ebyhr]

@raunaqmorarka Do you know why the DF timeout and the relevant logic were implemented on the connectors' side? (To avoid SPI change ConnectorSplitSource.getNextBatch, or allow different values per catalog?)