refactor(meta): maintain subscription information in job 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 in global barrier worker, we maintain the subscription information in InflightSubscriptionInfo separately to each streaming job. However, each subscription must be associated to a streaming job (table or MV), so it's more intuitive to maintain the subscription information inside InflightStreamingJobInfo.

Previously, the CN local barrier worker maintains a copy of the global subscription information and will clone and pass the global copy to each newly spawned actors for their MV executor to check whether there is initially subscription on the MV. After this PR, the CN local barrier worker won't maintain these information anymore. Instead, the information of initial subscription of an actor will be carried in the BuildActorInfo of each actor. The newly added field in BuildActorInfo will be filled in according to the subscription information maintained in the InflightStreamingJobInfo that the actor belongs to.

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.
• I have checked the Release Timeline and Currently Supported Versions to determine which release branches I need to cherry-pick this PR into.

Documentation

• My PR needs documentation updates.

Release note

[wenym1]

• feat(meta): global barrier worker concurrently reconnect to worker #23596
• refactor(meta): maintain subscription information in job info #23529 👈 (View in Graphite)
• main

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

[yezizp2012]

LGTM