Add an optimizer to add distinct below build side of semi join

[feilong-liu]

Description

We found that adding a distinct aggregation before a semi join on the build side can improve latency. This is probably due to the restriction that the build side of semi join is executed with single thread

presto/presto-main-base/src/main/java/com/facebook/presto/sql/planner/LocalExecutionPlanner.java

Line 2623 in a12b523

checkArgument(buildContext.getDriverInstanceCount().orElse(1) == 1, "Expected local execution to not be parallel");

This PR works by adding a distinct aggregation below the semi join on the build side.

Motivation and Context

To improve latency of semi join

Impact

To improve latency of semi join

Test Plan

Unit tests

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• 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
* Add an optimizer to add distinct aggregation on build side of semi join

[jaystarshot]

This can be on by default?

[feilong-liu]

I'd like to run it for some time before turning it on as default.

[jaystarshot]

Please add small comment explaining the rule

[feilong-liu]

#25254