[BugFix] fix setDouble issue in jdbc with prepare stmt

[ShaoxunLi]

Why I'm doing:

fix setDouble issue in jdbc with prepare stmt:

the result is wrong:

the reason is wrong type processing in FloatLiteral::parseMysqlParam.
For example, the data is of double type, but the getFloat method is used to obtain the data, result in wrong value.

What I'm doing:

When a new floatLiteral object is created, its type should be specified explicitly, not based on its numeric size.
Otherwise, when the data is small, it will be processed as the float type, even if the value is assigned by setDouble method in JDBC.

ths result is right:

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
• 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.3
  • 3.2
  • 3.1
  • 3.0
  • 2.5

[ShaoxunLi]

AnalysisException is deprecated, but the old method returns this exception.
How can I solve the codecheck error? @LiShuMing @satanson Thanks

[LiShuMing]

AnalysisException is deprecated, but the old method returns this exception. How can I solve the codecheck error? @LiShuMing @satanson Thanks

1. This should not affect this PR, right? This is just a reminder from your IDE?
2. Since AnalysisException is Deprecated, SemanticException is preferred in the future. But there are a lot of old codes left which are not changed.

[ShaoxunLi]

AnalysisException is deprecated, but the old method returns this exception. How can I solve the codecheck error? @LiShuMing @satanson Thanks

1. This should not affect this PR, right? This is just a reminder from your IDE?
2. Since AnalysisException is Deprecated, SemanticException is preferred in the future. But there are a lot of old codes left which are not changed.

It causes an error from SonarCloud Code Analysis:

and using SemanticException here will lead to lots of code changes

[satanson]

AnalysisException is deprecated, but the old method returns this exception. How can I solve the codecheck error? @LiShuMing @satanson Thanks

1. This should not affect this PR, right? This is just a reminder from your IDE?
2. Since AnalysisException is Deprecated, SemanticException is preferred in the future. But there are a lot of old codes left which are not changed.

The picture is invisible. errors reported by SonarCloud can be ignored

[ShaoxunLi]

AnalysisException is deprecated, but the old method returns this exception. How can I solve the codecheck error? @LiShuMing @satanson Thanks

1. This should not affect this PR, right? This is just a reminder from your IDE?
2. Since AnalysisException is Deprecated, SemanticException is preferred in the future. But there are a lot of old codes left which are not changed.

The picture is invisible. errors reported by SonarCloud can be ignored

ok，thank you
There seems to be some unstable test cases, i‘ll re-trigger the CI

[sonarcloud]

Quality Gate failed

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

See analysis details on SonarCloud

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

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

✅ pass : 4 / 4 (100.00%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/analysis/LiteralExpr.java	1	1	100.00%	[]
🔵	com/starrocks/analysis/FloatLiteral.java	3	3	100.00%	[]

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)