perf(storage): use VecDeque for TableChangeLog to avoid large clone on truncate

[wenym1]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

May alleviate the issue mentioned in #19960.

Previously we use Vec to store all table change log. When applying version delta, we use Vec::retain to clean the stale change log. However, for subscription with large retention time, the Vec can be large, and the Vec::retain called in truncate will incur great cost. In this PR, we change to use VecDeque to store the change log, so that the cost of truncate will reduce from O(N) to O(1).

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

[zwang28]

LGTM

[Li0k]

LGTM