Planner: Run full partition pruning if convertToPointGet converted keys to SortKey (#59918)

[ti-chi-bot]

This is an automated cherry-pick of #59918

What problem does this PR solve?

Issue Number: close #59827

Problem Summary:
When PointGetPlan is created by convertToPointGet, the IndexValues comes from the Range optimizer, and if any of the LIST/RANGE COLUMNS has a non-binary collation, they conditions values are converted to SortKey, which does not work with the LIST/RANGE COLUMNS partitioning pruning code, since they will unconditionally convert it again to SortKey, which may fail finding a matching partition.

NOTE: This only affects PointGet, since BatchPointGet is not supported yet.

What changed and how does it work?

If the IndexValues are already converted, run the normal partition pruning code on the conditions, to find the matching partition.

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.

Partition Pruning could fail and choose 'TableDual', i.e. no matching partition, in case the optimizer could convert the query to PointGet (if not using the FastPlan) and any LIST COLUMNS or RANGE COLUMNS had non-binary collation.

[codecov]

Codecov Report

Attention: Patch coverage is 69.72477% with 33 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.5@318fb14). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-8.5     #60162   +/-   ##
================================================
  Coverage               ?   56.9221%           
================================================
  Files                  ?       1769           
  Lines                  ?     628031           
  Branches               ?          0           
================================================
  Hits                   ?     357489           
  Misses                 ?     246420           
  Partials               ?      24122           

Flag	Coverage Δ
integration	36.7844% <30.2752%> (?)
unit	72.5948% <68.8073%> (?)

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

Components	Coverage Δ
dumpling	52.8711% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	52.2715% <0.0000%> (?)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mjonss, qw4990

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 [mjonss,qw4990]
• pkg/planner/OWNERS [qw4990]

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:

• 2025-04-09 22:42:36.636069119 +0000 UTC m=+2296250.320305218: ☑️ agreed by mjonss.
• 2025-04-14 16:56:49.132543429 +0000 UTC m=+2707502.816779510: ☑️ agreed by qw4990.