Extend join prefilter optimizer to use hash for filter

[feilong-liu]

Description

JoinPrefilter optimizer was added in #22667 which shows great improvement for a bunch of queries within Meta. However there are two limits of the current implementation

• When the join key is wide, for example VARCHAR type, the semi join added will have a high memory overhead
• It currently only supports single join key
  To solve the above limits, this PR:
• Use the hash of the join key for semi join when the join key is wide.
• When having multiple join keys, hash each key and combine the hash into a single key for semi join
  We can apply the hash as this pre filter is an opportunistic and does not need to be comprehensive.

Motivation and Context

To apply the join prefilter optimizer to more query shapes

Impact

Apply join prefilter to more query shapes

Test Plan

Add to existing plans
Also run verifier suites
This optimizer is default to be disabled as it's not always beneficial, we are considering using HBO to enable it in the future

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* Improve JoinPrefilter optimizer for wide join keys and multiple join keys :pr:`23858`

[jaystarshot]

nit: Can show the hash project here to explain

[feilong-liu]

Updated to cover all three cases

• one join key (not varchar type)
• one join key (varchar type)
• multiple join keys

[kaikalur]

Keep it simple and just do it always for varchar/char type?

[feilong-liu]

Updated

[feilong-liu]

@jaystarshot I have updated the code to address the test failure, can you take another look? Thanks!