feat(storage): wait committed epoch when update vnode bitmap

[wenym1]

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

What's changed and what's your intention?

Part of #18312

In this PR, on update_vnode_bitmap of LocalStateStore, we will explicitly wait for the previous epoch to be committed, so that after update_vnode_bitmap returns, the local state store is ready to be read, and doesn't depend on correctly calling try_wait_epoch outside of it.

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

[gru-agent]

❌ Rebase test pr failed: Error: Pull request #20492 is not created by gru-agent[bot]

[wenym1]

• feat(meta): do configuration change in single barrier #20493
• feat(storage): wait committed epoch when update vnode bitmap #20492 👈 (View in Graphite)
• refactor(log-store): update log store state vnode bitmap after yield barrier #20491
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[gru-agent]

❌ Rebase test pr failed: Error: Pull request #20492 is not created by gru-agent[bot]