scale: handle MV on MV when scaling

[BugenZhao]

There are some remaining tasks for scaling to handle MV on MV correctly.

• Ban scaling of "MV on MV" being created by introducing the table fragments state #5729
  The BatchQueryExecutor won't be paused when scaling now, so it's problematic to scale the downstream fragments.
• Allow scaling Materialize along with Chain for created "MV on MV". #5740
  This is the only case of no-shuffle exchange now. To support scaling them simultaneously, we can specify that only upstream Materialize is allowed to be the target of rescheduling.
• Support scaling of Sink #5856
• Bug: scaling chain fragment with DynamicFilter will fail #6292
  • DynamicFilter does not fetch the new range after the vnode map is updated  #6414 (in progress)

To be determined:

• Allow scaling of "MV on MV" being created.
  As a refinement of the first entry, it may help to speed up the creation process if needed. May implemented on Support backfill operator for mv on mv #6275.