planner, stats: overflow estimation may lead to wrong join reorder (#56752)

[ti-chi-bot]

This is an automated cherry-pick of #56752

What problem does this PR solve?

Issue Number: close #56704

Problem Summary:

What changed and how does it work?

When the width of the histogram is tooooo large, it's possible that right bound - left bound exceeds MaxFloat64. Then the width becomes inf, and the later calculation is likely to create NaN.

Join reorder uses MaxFloat64 to do the cost comparison, which leads to the wrong order in the above extreme case.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

Fix the case that the cost estimation may get INF/NaN in some extreme situations. And fix the wrong join reorder caused by this issue.
修复当代价估算在某些极端情况下估算出 INF/NaN 非法值的问题，以及该问题发生时 join reorder 可能结果出错的问题。

[codecov]

Codecov Report

Attention: Patch coverage is 47.05882% with 9 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-7.5@df753d1). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #56764   +/-   ##
================================================
  Coverage               ?   72.1521%           
================================================
  Files                  ?       1416           
  Lines                  ?     413285           
  Branches               ?          0           
================================================
  Hits                   ?     298194           
  Misses                 ?      95092           
  Partials               ?      19999           

Flag	Coverage Δ
unit	72.1521% <47.0588%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.9400% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.5302% <0.0000%> (?)

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, winoros

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [AilinKid,winoros]
• pkg/planner/OWNERS [AilinKid,winoros]
• pkg/statistics/OWNERS [AilinKid,winoros]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-12-12 15:07:38.902088919 +0000 UTC m=+537448.990891454: ☑️ agreed by winoros.
• 2024-12-12 16:00:05.308297608 +0000 UTC m=+540595.397100150: ☑️ agreed by AilinKid.