fix(upsert): use bounded file match filter to avoid scan planning segfault

[abnobdoss]

Summary

Use a bounded file match filter for the initial upsert target scan. The exact match filter remains in place for overwrite and insert filtering.

Why

Composite-key upserts can build very large exact predicate trees before scanning target files. On affected runtimes that recursive predicate shape can overflow during scan planning. The bounded filter keeps initial scan predicate size tied to the number of join columns instead of the number of source keys.

Testing

• Reproduced the base-branch failure locally with the large composite-key scan-planning path; the Python 3.10 subprocess exited 139
• uv run python -m pytest tests/table/test_upsert.py -k "large_composite_key_initial_scan or file_match_filter or create_match_filter"
• uv run python -m pytest tests/table/test_upsert.py
• commit hooks