[BugFix] Fix full outer join rewrite and nested mv refresh bug for main(#34071)

[ABingHuang]

For rewrite:

1. fix join derivibility rewrite bug for multi joins query
2. fix equivalence class construction bugs to exclude outer join on predicate, which should be rewritten by ReplaceColumnRefRewriter
3. optimize predicate normalization to process column name's case
4. set mv plan timeout to new_planner_optimize_timeout

For refresh:

1. fix refresh on nested mv bug to process date format like %Y%m%d
2. set strict mode to false for mv refresh

Fixes #issue

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

Bugfix cherry-pick branch check:

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

[starrocks-cr]

Here are my suggestions upon reviewing your code:

1. Error Handling: There's no handling for potential error(s) when parsing the date string, which might throw DateTimeParseException. You should handle this exception in order to prevent it from propagating upwards.

2. Code Duplication: There is some repetitive code occurring in both convertToDateRange and convertToVarcharRange. This especially holds true for the conditionals checking whether the range has upper and lower bound (both existing independently). To address this, consider refactoring these sections into their own methods. You can create helper functions to carry out these tasks.

3. Type Checks: The instance type checks with instanceof DateLiteral or instanceof StringLiteral can potentially become problematic if more types are to be supported later on. Consider using a strategy pattern or similar approach for dealing with different types.

4. Comments: While you have done well to comment your methods, you could improve readability by also describing what the function does in general, not just talking about specific implementation details. These comments will be beneficial for people reading your code, especially people new to the project.

5. Magic Numbers: The use of .getKeys().get(0) suggests there may be magic numbers being used in your code. This might make your code less understandable and difficult to maintain. If the 0 index has a special significance, either comment it well or factor out a constant with an explanatory name.

6. Safe Unwrapping: When unpacking values from complex objects like from.lowerEndpoint().getKeys().get(0), there's an assumption that every step retrieves a non-null value. Consider including null-checks or use Optional types to avoid NullPointerExceptions.

7. Method Naming: The method names such as convertToDateRange and convertToVarcharRange are good and descriptive. Good job on this!

Overall your code seems well-structured, other than these few areas that could be enhanced.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
14 Code Smells

0.0% Coverage
0.0% Duplication

The version of Java (11.0.21) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17.
Read more here

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 148 / 153 (96.73%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/scheduler/PartitionBasedMvRefreshProcessor.java	22	25	88.00%	[1213, 1214, 1261]
🔵	com/starrocks/sql/optimizer/rule/transformation/materialization/MvUtils.java	25	26	96.15%	[1254]
🔵	com/starrocks/sql/optimizer/rule/transformation/materialization/MaterializedViewRewriter.java	89	90	98.89%	[407]
🔵	com/starrocks/sql/optimizer/rewrite/scalar/MvNormalizePredicateRule.java	4	4	100.00%	[]
🔵	com/starrocks/sql/optimizer/MvPlanContextBuilder.java	4	4	100.00%	[]
🔵	com/starrocks/sql/optimizer/rule/mv/JoinDeriveContext.java	4	4	100.00%	[]