statistics: fix "data too long" error when dumping stats from table with new collation data

[time-and-fate]

What problem does this PR solve?

Issue Number: close #27024

When storing a histogram for a new collation column, we store its collate key instead of the original value.
However (1) when loading the histogram into stats cache, we try to convert the bounds of the histogram to the FieldType of this column (2) the collate key of a value is usually longer than the original value.
So when doing the type conversion, the value may exceed the FieldType.Flen, which caused the "Data Too Long" error.

What is changed and how it works?

When loading stats from storage into stats cache, for String values, no longer convert them to the FieldType of this column.
Now we always convert them to TypeBlob to bypass length checks.

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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• eurekaka
• winoros

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.

[time-and-fate]

/sig planner
/component statistics

[time-and-fate]

/run-check_dev_2

[time-and-fate]

/label needs-cherry-pick-5.2
/label needs-cherry-pick-5.1
/label needs-cherry-pick-5.0
/label needs-cherry-pick-4.0

[ti-chi-bot]

@time-and-fate: The label(s) needs-cherry-pick-5.2 cannot be applied. These labels are supported: CHANGELOG, challenge-program, compatibility-breaker, contribution, correctness, first-time-contributor, good-first-issue, hacktoberfest, high-performance, hptc, need-more-info, needs-cherry-pick-3.0, needs-cherry-pick-3.1, needs-cherry-pick-4.0, needs-cherry-pick-5.0, needs-cherry-pick-5.1, proposal, release-note, require-LGT3, security, tools.

In response to this:

/label needs-cherry-pick-5.2
/label needs-cherry-pick-5.1
/label needs-cherry-pick-5.0
/label needs-cherry-pick-4.0

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 ti-community-infra/tichi repository.

[time-and-fate]

/label needs-cherry-pick-5.2

[ti-chi-bot]

@time-and-fate: The label(s) needs-cherry-pick-5.2 cannot be applied. These labels are supported: CHANGELOG, challenge-program, compatibility-breaker, contribution, correctness, first-time-contributor, good-first-issue, hacktoberfest, high-performance, hptc, need-more-info, needs-cherry-pick-3.0, needs-cherry-pick-3.1, needs-cherry-pick-4.0, needs-cherry-pick-5.0, needs-cherry-pick-5.1, proposal, release-note, require-LGT3, security, tools.

In response to this:

/label needs-cherry-pick-5.2

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 ti-community-infra/tichi repository.

[winoros]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: c571a37

[ti-srebot]

cherry pick to release-4.0 in PR #27299

[ti-srebot]

cherry pick to release-5.0 in PR #27300

[ti-srebot]

cherry pick to release-5.1 in PR #27301

[ti-srebot]

cherry pick to release-5.2 in PR #27302