[FLINK-37139][table-planner] Improve AdaptiveSkewedJoinOptimizationStrategy to make it effective in more scenarios

[noorall]

What is the purpose of the change

Currently, the scenarios in which the AdaptiveSkewedJoinOptimizationStrategy is effective are too limited. For example, when there is an output edge of the forward for unspecified type, the optimization cannot be applied. However, this optimization wouldn't break the data correctness of this kind output edges. Therefore, we will optimize this scenario to enable the optimization to be effective in more scenarios.

Brief change log

Improve AdaptiveSkewedJoinOptimizationStrategy to make it effective in more scenarios.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
• The serializers: (yes / no / don't know)
• The runtime per-record code paths (performance sensitive): (yes / no / don't know)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
• The S3 file system connector: (yes / no / don't know)

Documentation

• Does this pull request introduce a new feature? (yes / no)
• If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

[zhuzhurk]

LGTM.

[flinkbot]

CI report:

• e2e25bf Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[JunRuiLee]

LGTM