Add BloomFilter PhysicalExpr

### Is your feature request related to a problem or challenge?

Related to #15512

I think this is a first step towards HashJoinExec pushdown. I think we should model that as `col >= hash_table_min AND col <= hash_table_max AND hash_table_bloom(col)`. The simple bounds should help with stats pruning, etc.

I believe we could also use this to accelerate `IN ` and re-use the code for bloom filter pruning in parquet scans (just for code reuse)

Start with related issue #15512 and the existing PhysicalExpr and parquet bloom-filter pruning paths mentioned here. Clarify the intended scope for HashJoinExec pushdown, IN , and code reuse before implementation; done should be a reviewed BloomFilter PhysicalExpr with tests for the agreed integrations.

Written by the indexing model from the issue text.