[Improve][Zeta] Move SaveMode behavior to master

[Hisoka-X]

Purpose of this pull request

This PR move savemode logic into master node.
Mainly for two purposes:

1. Maintain the same behavior as the Rest submit job. Before this, the SaveMode logic of Rest mode was executed on the master, but the client mode was executed on the client side.
2. Prepare for related SaveMode event processing. Based on purpose 1, we can ensure consistent behavior of SaveMode related events.

Does this PR introduce any user-facing change?

no

How was this patch tested?

add new test.

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 change log that in connector document. For more details you can refer to connector-v2
  2. Update plugin-mapping.properties and add new connector information in it
  3. Update the pom file of seatunnel-dist
• Update the release-note.

[dailai]

Should we consider the DataSerializable of this?

[Hisoka-X]

In fact, the current SupportSaveMode declarations are all on the SeaTunnelSink implementation class, and all SeaTunnelSinks are serializable by default. It is also engine-independent.