POC Make BloomFilter application general, add PruningPredicate::contains

[alamb]

Which issue does this PR close?

POC for #8376

Rationale for this change

See #8376

TLDR is I would like to use PruningPredicate for "bloom filter like" operations downstream in IOx, and thus I would like to refactor the code that applies Bloom Filters today into the PruningPredicate.

What changes are included in this PR?

1. New PruningStatistics::contains API proposed in Support general pruning based on <col> = 'const' in PruningPredicate #8376
2. Add LiteralGuarantee for extracting col = <const> predicates, along with many new tests
3. Rewrite the BloomFilter code to use the new predicate API

TODO

• File a follow on ticket for actual support of IN and NOT IN exprs. Support IN lists with more than three constants in predicates for bloom filters #8436

Are these changes tested?

• New tests for PruningPredicate contains (=, !=, = with OR, IN and NOT IN)
• Existing tests pass

Are there any user-facing changes?

The PruningPredicate has a new API

Plans for merging

I do not plan to propose merging this PR as is. Instead I plan a series of PRs:

1. A PR with some new bloom filter tests
2. A PR that introduces the contains API with tests
3. A second PR that refactors the the row group pruning code to use it
4. A third PR that refactors the RowGroupPruning code so it runs on more than one RowGroupMetadatat at a time.

🤔 musing: At the moment, the row group pruning happens in two phases -- first the min/max statistics are applied, and then the bloom filters are applied which means the potentially bloom filters are only fetched for groups that passed the first predicate.

[alamb]

The pieces of this PR are in, so closing this PR and focusing on merging the parts