refactor(meta): deprecate persisted actor upstreams and get upstreams from dispatcher info

[wenym1]

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

What's changed and what's your intention?

Previously we persist both the dispatchers of upstream actors, and the actor upstream info of downstream actors in meta store. However, these two information should be semantically identical and duplicated, and we have to carefully maintain their consistency in our code.

In this PR, we will deprecate persisting the actor upstreams in the Actor table. In the original place to use it, we will always extract the actor upstreams information by the dispatcher info along with it. More specifically, we implement a method collect_actor_upstreams, which will generate the actor upstream information when we provide sufficient dispatcher information.

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
• 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 👈 (View in Graphite)
• 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.

[gru-agent]

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

[yezizp2012]

LGTM! Cc @shanicky PTAL, it should be related to the refactoring that you're working.

[shanicky]

LGTM