refactor(meta): deprecate persisted fragment upstream ids

[wenym1]

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

What's changed and what's your intention?

With fragment_relation table introduced, the upstream_fragment_id in fragment table becomes redundant. In this PR, we will deprecate the usage on this column.

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

[wenym1]

• refactor(meta): deprecate persisted fragment upstream ids #20548 👈 (View in Graphite)
• refactor(meta): deprecate dispatcher table and compose dispatcher by fragment relation #20541
• refactor(meta): deprecate persisted actor upstreams and get upstreams from dispatcher info #20387
• feat(meta): let stream actors in fragment share same stream node #20310
• refactor: make actor graph builder fragment aware #20385
• refactor(meta): do not store upstream actors in merge node #20222
• main

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

[yezizp2012]

LSTM! The dashboard also needs to be updated accordingly.

[BugenZhao]

Are we going to remove this field?

[wenym1]

May keep it for a release and remove it in the next release.