lowerUTF8/upperUTF8 allow lower/uppercase characters occupy different number of bytes (#8622)

[ti-chi-bot]

This is an automated cherry-pick of #8622

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

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gengliqi, Lloyd-Pottiger

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 [Lloyd-Pottiger,gengliqi]

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-24 11:44:49.774276502 +0000 UTC m=+961131.338574193: ☑️ agreed by gengliqi.
• 2024-01-26 05:27:29.842406141 +0000 UTC m=+1111291.406703831: ☑️ agreed by Lloyd-Pottiger.