workaround for performance regression in DuckDB v1.3.0

[danabauer]

Max Gabrielsson from DuckDB Labs shared this in the Cloud Native Geospatial slack this morning:

"If you're using DuckDB to read remote Geoparquet files (e.g. overture) relying on bounding-box-filtering and experiencing performance regressions in v1.3.0 you need to add an additional set of conditions to your WHERE clause: ... AND bbox.xmax < 'nan' and bbox.ymax < 'nan' More info here"

[danabauer]

Fixed in the v1.3.1 release!

https://github.com/duckdb/duckdb/releases/tag/v1.3.1