lowerUTF8/upperUTF8 allow lower/uppercase characters occupy different number of bytes

[gengliqi]

What problem does this PR solve?

Issue Number: close #8484

Problem Summary:
See #8484.

What is changed and how it works?

1. lowerUTF8/upperUTF8 allow lower/uppercase characters occupy different number of bytes
2. lowerUTF8/upperUTF8 respect the row boundaries, which means invalid sequences do not influence other rows. Inspired by Do not allow invalid sequences influence other rows in lowerUTF8/upperUTF8 ClickHouse/ClickHouse#41286.

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

Fix the bug that lowerUTF8/upperUTF8 do not allow lower/uppercase characters occupy different number of bytes

[gengliqi]

/run-all-tests

[windtalker]

LGTM

[gengliqi]

/run-all-tests

[SeaRise]

Others LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: SeaRise, windtalker

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 [SeaRise,windtalker]

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:

• 2024-01-02 09:20:41.438045985 +0000 UTC m=+2162332.475272911: ☑️ agreed by windtalker.
• 2024-01-04 10:39:57.602964708 +0000 UTC m=+2339888.640191621: ☑️ agreed by SeaRise.

[gengliqi]

/run-all-tests

[Lloyd-Pottiger]

/run-integration-test

[SeaRise]

/run-integration-test

[ti-chi-bot]

@gengliqi: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-5.4: #8665.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #8666.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #8667.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #8668.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #8669.