Cherry pick sm4

[lidezhu]

What problem does this PR solve?

Issue Number: close #xxx

Problem Summary: cherry pick of tikv#12927

What is changed and how it works?

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 4 committers have signed the CLA.

✅ lidezhu
✅ CalvinNeo
❌ jiayang-zheng
❌ BusyJay
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CalvinNeo]

lgtm

[CalvinNeo]

It compiles #161, if we just run these two

cargo test --package tests --test proxy normal::store
cargo test --package tests --test proxy proxy

Since we have noticed in failed run

2022-09-07T12:39:03.3004142Z test cases::test_merge::test_merge_election_and_restart ... ok
2022-09-07T12:39:04.9594125Z test cases::test_merge::test_merge_pessimistic_locks_propose_fail ... ok
2022-09-07T12:39:06.6658756Z test cases::test_merge::test_merge_pessimistic_locks_with_concurrent_prewrite ... ok
2022-09-07T12:39:07.9850167Z test cases::test_merge::test_merge_with_concurrent_pessimistic_locking ... ok
2022-09-07T12:39:09.4607278Z test cases::test_merge::test_node_failed_merge_before_succeed_merge ... ok
2022-09-07T12:39:10.5816694Z test cases::test_merge::test_node_merge_cascade_merge_with_apply_yield ... ok
2022-09-07T12:39:11.9267893Z test cases::test_merge::test_node_merge_catch_up_logs_leader_election ... ok
2022-09-07T12:39:15.8692784Z test cases::test_merge::test_node_merge_catch_up_logs_no_need ... ok
2022-09-07T12:39:16.6930253Z test cases::test_merge::test_node_merge_catch_up_logs_restart ... ok
2022-09-07T12:39:18.0882430Z test cases::test_merge::test_node_merge_crash_before_snapshot_then_catch_up_logs ... ok
2022-09-07T12:39:21.7773265Z test cases::test_merge::test_node_merge_crash_when_snapshot ... ok
2022-09-07T12:39:24.0349623Z test cases::test_merge::test_node_merge_multiple_snapshots_not_together ... ok
2022-09-07T12:39:26.2794137Z test cases::test_merge::test_node_merge_multiple_snapshots_together ... ok
2022-09-07T12:39:29.5354972Z test cases::test_merge::test_node_merge_recover_snapshot ... ok
2022-09-07T12:39:31.3359905Z test cases::test_merge::test_node_merge_restart ... ok
2022-09-07T12:39:32.4962158Z test cases::test_merge::test_node_merge_restart_after_apply_premerge_before_apply_compact_log ... ok
2022-09-07T12:39:36.3183283Z test cases::test_merge::test_node_merge_rollback ... ok
2022-09-07T12:39:37.2580543Z test cases::test_merge::test_node_merge_transfer_leader ... ok
2022-09-07T12:39:38.5871725Z test cases::test_merge::test_node_merge_write_data_to_source_region_after_merging ... ok
2022-09-07T12:39:40.3785568Z test cases::test_merge::test_node_multiple_rollback_merge ... ok
2022-09-07T12:39:41.4501365Z test cases::test_merge::test_prewrite_before_max_ts_is_synced ... ok
2022-09-07T12:39:42.7610457Z test cases::test_merge::test_retry_pending_prepare_merge_fail ... ok
2022-09-07T12:39:43.3550686Z test cases::test_merge::test_source_peer_read_delegate_after_apply ... ok
2022-09-07T12:39:43.3551411Z 
2022-09-07T12:39:43.3551915Z test result: ok. 23 passed; 0 failed; 0 ignored; 0 measured; 166 filtered out; finished in 42.76s

I think this failure is because we exceed what GitHub Action's runner can afford.

Maybe we can split this ci check into two.