planner: fix the incorrect int pk null range for tici

[winoros]

this is a second try. for the case that pk column is not read

What problem does this PR solve?

Issue Number: ref #64651

Problem Summary:

What changed and how does it work?

The previous pr didn't cover all cases.
It's still possible to generate the wrong range if the pk column is not needed by the operator.

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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ailinkid for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

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

Details

Needs approval from an approver in each of these files:

• pkg/planner/OWNERS

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

[codecov]

Codecov Report

❌ Patch coverage is 20.00000% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 70.6781%. Comparing base (2d2bd57) to head (b57fa68).
⚠️ Report is 48 commits behind head on feature/fts.

Additional details and impacted files

@@                 Coverage Diff                 @@
##           feature/fts     #66006        +/-   ##
===================================================
- Coverage      72.3094%   70.6781%   -1.6313%     
===================================================
  Files             1895       1873        -22     
  Lines           533272     526461      -6811     
===================================================
- Hits            385606     372093     -13513     
- Misses          123717     131905      +8188     
+ Partials         23949      22463      -1486     

Flag	Coverage Δ
integration	40.0050% <20.0000%> (-6.2743%)	⬇️

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

Components	Coverage Δ
dumpling	52.8700% <ø> (ø)
parser	∅ <ø> (∅)
br	46.2585% <ø> (-16.7802%)	⬇️

🚀 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]

@winoros: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/mysql-test	b57fa68	link	true	/test mysql-test
pull-integration-tici-test	b57fa68	link	false	/test pull-integration-tici-test
idc-jenkins-ci-tidb/unit-test	b57fa68	link	true	/test unit-test

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.