Fix potential data loss for tombstoned table (#1010)

[ti-srebot]

cherry-pick #1010 to release-3.1
You can switch your code base to this Pull Request by using git-extras:

# In tics repo:
git pr https://github.com/pingcap/tics/pull/1661

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tics.git pr/1661:release-3.1-7cfe93ddb714

---

What problem does this PR solve?

Issue Number: close #1007

Problem Summary:

What is changed and how it works?

What's Changed:

• Do write the data into storage even if it is tombstoned.

Related changes

• PR to update pingcap/docs/pingcap/docs-cn: none
• Need to cherry-pick to the release branch: 4.0, 3.1.

Check List

Tests

• Integration test

Side effects

• None

Release note

• Fix potential data loss when recovering a table that is previously dropped.

[JaySon-Huang]

Close it because we don't maintain the branch release-3.1