[Enhancement] Estimate cardinality of multiple equivalent predicates using multi-column combined stats

[stephen-shelby]

Why I'm doing:

What I'm doing:

major changes:

1. adjust the calculation method of multiple equivalent predicates cardinality estimation without multi-column stats
2. estimate cardinality of multiple equivalent predicates using multi-column combined stats

without multi-columns stats

• use up to 4 equivalent predicates with the best filtering performance
• Considering the correlation between columns, use the decreasing formula ref to SQL Server.
  Sel(p1 ∧ p2 ∧ p3) = Sel(p1) × Sel(p2)^{1/2} × Sel(p3)^{1/4}

Multi-column combined statistics based:
S_mc = max(min(1/NDV, min_sel), prod_sel)
Where:
1/NDV is the selectivity based on multi-columns ndv
min_sel is the minimum selectivity among correlated columns
prod_sel is the product of individual column selectivities

added session variable:
cbo_use_correlated_predicate_estimate
if use decreasing formula for CE. default value is true.

Fixes #issue
#56358

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.4
  • 3.3
  • 3.2
  • 3.1
  • 3.0

[sonarqubecloud]

Quality Gate failed

Failed conditions
B Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 112 / 114 (98.25%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/sql/optimizer/statistics/StatisticsEstimateUtils.java	86	88	97.73%	[93, 129]
🔵	com/starrocks/qe/SessionVariable.java	4	4	100.00%	[]
🔵	com/starrocks/sql/optimizer/Utils.java	13	13	100.00%	[]
🔵	com/starrocks/sql/optimizer/statistics/BinaryPredicateStatisticCalculator.java	1	1	100.00%	[]
🔵	com/starrocks/sql/optimizer/statistics/PredicateStatisticsCalculator.java	8	8	100.00%	[]

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)