[Improve][Zeta] Add configuration option for physical DAG

[dybyte]

Purpose of this pull request

• Introduce a new configuration option physical-dag-enabled that allows users to control whether the engine generates and executes a physical DAG (optimized for execution), or uses the logical DAG as defined in the configuration.

• Fix a bug in pipeline lookup logic where key comparison used different types, which could cause failures when mapping logical DAG vertices to pipelines.

Does this PR introduce any user-facing change?

Yes. Users can now use the new configuration option physical-dag-enabled to control DAG execution mode.
The default value maintains backward compatibility.

How was this patch tested?

I verified that JobDAGInfo outputs differ between physical-dag-enabled = true and physical-dag-enabled = false with a new test case.

Check list

• If any new Jar binary package adding in your PR, please add License Notice according
  New License Guide
• If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
• If you are contributing the connector code, please check that the following files are updated:
  1. Update plugin-mapping.properties and add new connector information in it
  2. Update the pom file of seatunnel-dist
  3. Add ci label in label-scope-conf
  4. Add e2e testcase in seatunnel-e2e
  5. Update connector plugin_config

[Hisoka-X]

what's different of behavior of engine or job when enable or disable physical-dag-enabled? Or what benefits will this bring to users?

[dybyte]

what's different of behavior of engine or job when enable or disable physical-dag-enabled? Or what benefits will this bring to users?

The engine or job behavior does not change depending on the physical-dag-enabled setting.
This option only controls whether the user sees the physical DAG info or the logical DAG info for visualization. I misunderstood this before.
In fact, the code to show the logical DAG was implemented long ago in #3649 , but since isPhysicalDAGInfo was always set to true, this logic was never actually used until now. @Hisoka-X

[dybyte]

I think we may also need to update this file: RestHttpGetCommandProcessor.java.
Do you think that's correct?

[Hisoka-X]

This option only controls whether the user sees the physical DAG info or the logical DAG info for visualization

So I think we should not add an config in seatunnel.yaml for this. We can only support it in restful api, WDYT?

[dybyte]

So I think we should not add an config in seatunnel.yaml for this. We can only support it in restful api, WDYT?

I agree. Should we support it in restful api and client too?

[Hisoka-X]

I agree. Should we support it in restful api and client too?

LGTM :)