fix row key not in standard format (#7901)

[ti-chi-bot]

This is an automated cherry-pick of #7901

What problem does this PR solve?

Issue Number: close #3099 close #7762

Problem Summary: For int handle, the standard row key format should be t{tidb_id}_r{row_id}, but the cluster may generate keys not strictly adhere to this format. For example, it may append a 0x00 to the encoded value.
When tiflash decode the key, it will ignore the suffix 0x00 and may get an invalid row key value.

What is changed and how it works?

For row key which size is larger than the standard format, we add 1 on the decoded int key value.
This is ok, because

1. if the key is the start range, then [t100_r1000 + 0x00, xxx) has the same semantics with [t100_r1001, xxx)
2. if the key is the end range, then [xxx, t100_r1000 + 0x00) also has the same semantics with [xxx, t100_r1001)

Note if the decoded int value is Int64::max_value, it is a value generated by tiflash itself which is RowKeyValue::INT_HANDLE_MAX_KEY. This is a special key to means +inf, so we can just ignore it.

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 potential consistency problem when the int type row key value is not in standard encoding format

[lidezhu]

/run-all-tests

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, lidezhu

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 [JaySon-Huang,lidezhu]

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:

• 2023-08-09 05:45:28.61152087 +0000 UTC m=+91493.160536858: ☑️ agreed by JaySon-Huang.
• 2023-08-09 10:48:56.023891377 +0000 UTC m=+109700.572907364: ☑️ agreed by lidezhu.