linter: enable intrange for planner

[hawkingrei]

What problem does this PR solve?

Issue Number: ref #40786

Problem Summary:

What changed and how does it work?

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 33.33333% with 2 lines in your changes missing coverage. Please review.

Project coverage is 73.4664%. Comparing base (5ba9e6f) to head (397c5ef).
Report is 3 commits behind head on master.

❗ Current head 397c5ef differs from pull request most recent head 597e256

Please upload reports for the commit 597e256 to get more accurate results.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #58867        +/-   ##
================================================
+ Coverage   73.0449%   73.4664%   +0.4215%     
================================================
  Files          1689       1689                
  Lines        466944     466983        +39     
================================================
+ Hits         341079     343076      +1997     
+ Misses       104887     102930      -1957     
+ Partials      20978      20977         -1     

Flag	Coverage Δ
integration	42.8179% <33.3333%> (?)

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	45.3388% <ø> (+0.0057%)	⬆️

[zimulala]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lance6716, zimulala
Once this PR has been reviewed and has the lgtm label, please ask for approval from hawkingrei, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS [lance6716,zimulala]
• 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

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-01-13 06:43:48.391922553 +0000 UTC m=+767971.680754259: ☑️ agreed by lance6716.
• 2025-01-23 03:28:21.705611946 +0000 UTC m=+324229.036531350: ☑️ agreed by zimulala.

[tiprow]

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

Test name	Commit	Details	Required	Rerun command
fast_test_tiprow	597e256	link	true	/test fast_test_tiprow

Full PR test history. Your PR dashboard.

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.

[ti-chi-bot]

@hawkingrei: 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/unit-test	597e256	link	true	/test unit-test
idc-jenkins-ci-tidb/build	597e256	link	true	/test build
idc-jenkins-ci-tidb/mysql-test	597e256	link	true	/test mysql-test
idc-jenkins-ci-tidb/check_dev_2	597e256	link	true	/test check-dev2
idc-jenkins-ci-tidb/check_dev	597e256	link	true	/test check-dev

Full PR test history. Your PR dashboard.

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.