[Enhancement] split Metric "query_error" into there part

[before-Sunrise]

Why I'm doing:

#50250 add query internal error and query analysis error in FE metric, which is part of query error. But has some problem which already exists befor 50250:

1. when query timeout, it will count to analysis error, becasue it throws UserException
2. if one query fails in parser, no query error will be record, because at this time, ctx.getState().isQuery() is false
3. some UserException doesn't belong to analysis error, we should set such error type to internal error. Key point is some UserException actually is not user' s probelm sucn as "BE is down but we throw DdlException which is a UserException"

What I'm doing:

1. Fixes problem 1 and problem 2
2. add three error rate metric: internal error rate, analysis error rate, timeout rate
3. for problem 3, just fix what i konw: "BE is down but we throw DdlException which is a UserException"

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

[sonarcloud]

Quality Gate passed

Issues
15 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[FE Incremental Coverage Report]

❌ fail : 35 / 47 (74.47%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/common/Status.java	0	3	00.00%	[150, 151, 152]
🔵	com/starrocks/qe/ResultReceiver.java	0	1	00.00%	[150]
🔵	com/starrocks/qe/StmtExecutor.java	3	8	37.50%	[757, 759, 2328, 2332, 2338]
🔵	com/starrocks/common/ErrorReport.java	1	2	50.00%	[109]
🔵	com/starrocks/qe/DefaultCoordinator.java	1	2	50.00%	[913]
🔵	com/starrocks/qe/ConnectProcessor.java	2	3	66.67%	[223]
🔵	com/starrocks/metric/MetricRepo.java	9	9	100.00%	[]
🔵	com/starrocks/qe/QueryState.java	1	1	100.00%	[]
🔵	com/starrocks/metric/MetricCalculator.java	18	18	100.00%	[]

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[silverbullet233]

How should we find out this kind of error?

[github-actions]

@Mergifyio backport branch-3.3

[mergify]

backport branch-3.3

✅ Backports have been created

• #52788 [Enhancement] split Metric "query_error" into there part (backport #52646) has been created for branch branch-3.3