planner: Columns in string pruning (#32626) (#32721)

[ti-srebot]

cherry-pick #32721 to release-5.2
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/32925

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/32925:release-5.2-7bf5e4e23ea0

---

What problem does this PR solve?

Issue Number: close #32626

Problem Summary:

What is changed and how it works?

Only int and time type of columns was enabled to prune partitions in RANGE COLUMNS IN conditions.

This also enables String type columns

Check List

Tests

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

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

Enable partition pruning for RANGE COLUMNS partitioning on IN conditions and string type columns

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-srebot]

/run-all-tests

[ti-srebot]

@mjonss you're already a collaborator in bot's repo.

[mjonss]

Blocked by #31863 (needed to resolve merge conflict, depending on the support for IN partition pruning).

[VelocityLight]

This pull request is closed because it's related version has closed automatic cherry-picking.
If it's still needed, you can reopen it or just regenerate it using bot,
see:

• https://prow.tidb.io/command-help#cherrypick
• https://book.prow.tidb.net/#/plugins/cherrypicker

You can find more details at:

• https://internals.tidb.io/t/topic/785