util/ranger: Handle boundary value correctly in ranger to avoid incorrect tableDual plan (#52225)

[ti-chi-bot]

This is an automated cherry-pick of #52225

What problem does this PR solve?

Issue Number: close #50051

Problem Summary:

The function excludeToIncludeForIntPoint should deal with the boundary value correctly.

What changed and how does it work?

I guess it is not a bad idea to change the type of the point in this 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.

None

[codecov]

Codecov Report

Attention: Patch coverage is 66.66667% with 2 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-6.5@335e834). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-6.5     #53319   +/-   ##
================================================
  Coverage               ?   74.5230%           
================================================
  Files                  ?       1097           
  Lines                  ?     360270           
  Branches               ?          0           
================================================
  Hits                   ?     268484           
  Misses                 ?      75040           
  Partials               ?      16746           

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, wjhuang2016

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 [hawkingrei,wjhuang2016]

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-06-05 01:30:31.075198696 +0000 UTC m=+3431184.832334269: ☑️ agreed by hawkingrei.
• 2024-06-05 03:18:37.768842133 +0000 UTC m=+3437671.525977711: ☑️ agreed by wjhuang2016.