feat: at most one snapshot is written for one table in multi statement transaction

[SkyFan2002]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

If a table is updated multiple times in a mutli statement transaction, only one snapshot should be written to storage layer. This PR maintains a property: For any snapshot s, s.prev != null => s.prev must have been successfully committed, which will be the basis of the new vacuum protocol

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - Explain why

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is 

[SkyFan2002]

replaced by #16044