*: Make use of the upperBound of ticlient's kv_scan interface to ensure no overbound scan will happen (#8081)

[MyonKeminta]

What problem does this PR solve?

This PR cherry-picks #8081 (09c6bff) to release-2.0 branch to fix the bug that scanning out-of-range may cause TiKV

This PR requires merging #8309 first.

What is changed and how it works?

This PR cherry-picks #8081 (09c6bff) to release-2.0 branch.

Check List

Tests

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

  • Manually confirm that TiKV won't panic while executing add index or admin check table.

    1. Create two tables t1 and t2, insert some data in to them (values' length is large enough)
    2. Check t1 and t2's table_id (0x21 and 0x23)
    3. Delete some keys of t2 from default_cf by using RawKv API

       keys, _, err := cli.Scan([]byte("t\x80\x00\x00\x00\x00\x00\x00\xff\x23"), 3)
       if err != nil {
           panic(err)
       }
       
       for _, k := range keys {
           cli.Delete(k)
       }

    4. Try alter table t1 add index i1(id) and admin check table t1 in both current release-2.0 and this PR.

    Test result: In current release 2.0 branch TiKV will panic, while in this PR nothing strange happens.

Code changes

• None of those listed

Side effects

• Increased code complexity

Related changes

• Need to be included in the release note

---

This change is 

[MyonKeminta]

/run-all-tests pd=release-2.0 tikv=pr/3780 tidb-test=release-2.0

[MyonKeminta]

/run-unit-test

[MyonKeminta]

/run-all-tests pd=release-2.0 tikv=release-2.0 tidb-test=release-2.0

[zz-jason]

LGTM

[MyonKeminta]

@winkyao PTAL

[winkyao]

LGTM