feat(streaming): recover no_shuffle_backfill

[kwannoel]

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

What's changed and what's your intention?

• Recover current_pos from state_table.
• Also recover CreateMviewProgress, on recovery. For those which are already finished, they will still update their progress, and call finish, so the materialized view tracker can recover their progress.
• Also we shouldn't need to commit state table anymore, once backfill is finished. So we remove that logic as well.
• In this PR we also refactor the recovery logic. Previously current_pos, is_finished, and row_count are recovered separately. Now we recover them together, and handle backwards compatibility in recover_backfill_state.

This PR is a prerequisite of: #12167

we run a manual test in that PR #12167 to make sure we can recover the progress of an MV.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[codecov]

Codecov Report

Merging #12493 (cd4e3d5) into main (063f58e) will decrease coverage by 0.01%.
Report is 14 commits behind head on main.
The diff coverage is 3.57%.

@@            Coverage Diff             @@
##             main   #12493      +/-   ##
==========================================
- Coverage   69.41%   69.41%   -0.01%     
==========================================
  Files        1429     1429              
  Lines      238590   238598       +8     
==========================================
+ Hits       165621   165622       +1     
- Misses      72969    72976       +7     

Flag	Coverage Δ
rust	69.41% <3.57%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
...ream/src/executor/backfill/arrangement_backfill.rs	0.00% <ø> (ø)
src/stream/src/executor/backfill/utils.rs	9.97% <ø> (+1.14%)	⬆️
src/stream/src/executor/chain.rs	89.15% <ø> (ø)
src/stream/src/executor/rearranged_chain.rs	0.00% <ø> (ø)
src/stream/src/executor/values.rs	90.69% <ø> (ø)
...c/stream/src/task/barrier_manager/managed_state.rs	83.24% <0.00%> (ø)
src/stream/src/task/barrier_manager/progress.rs	53.42% <42.85%> (-1.51%)	⬇️
src/meta/src/barrier/progress.rs	7.65% <0.00%> (-0.08%)	⬇️
...tream/src/executor/backfill/no_shuffle_backfill.rs	0.00% <0.00%> (ø)

... and 1 file with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[chenzl25]

LGTM