test: shouldn't invoke committed callbacks when failing to commit (#9490)
test: shouldn't invoke committed callbacks when failing to commit (#9490)

Signed-off-by: youjiali1995 <c0aa3f5eb42bd3bf1adeeced4b718fc1900fde64@gmail.com>

<!--
Thank you for contributing to TiKV!

If you haven't already, please read TiKV's [CONTRIBUTING](https://github.com/tikv/tikv/blob/master/CONTRIBUTING.md) document.

If you're unsure about anything, just ask; somebody should be along to answer within a day or two.

PR Title Format:
1. module [, module2, module3]: what's changed
2. *: what's changed

If you want to open the **Challenge Program** pull request, please use the following template:
https://raw.githubusercontent.com/tikv/.github/master/.github/PULL_REQUEST_TEMPLATE/challenge-program.md
You can use it with query parameters: https://github.com/tikv/tikv/compare/master...${you branch}?template=challenge-program.md
-->

### What problem does this PR solve?

Problem Summary:

https://github.com/tikv/tikv/pull/9136 only has unit tests. Need an integration test.

### What is changed and how it works?

What's Changed:
Add an integration test to cover https://github.com/tikv/tikv/issues/9070:
1. Partition the leader and followers.
2. Propose a write request on the leader.
3. A new leader is elected and commits a new entry.
4. Recover the network partition.
5. The old proposal should be dropped and the committed_cb shouldn't be invoked.


### Related changes


### Check List <!--REMOVE the items that are not applicable-->

Tests <!-- At least one of them must be included. -->

- Unit test

### Release note <!-- bugfixes or new feature need a release note -->
* No release note
BusyJay/tikv,c4pt0r/tikv,BusyJay/tikv,BusyJay/tikv,BusyJay/tikv