[Fix][Zeta] Fix unnecessary job state update

[dybyte]

Purpose of this pull request

When stateProcess() inside updateJobState(JobStatus.PENDING) is executed as isRunning becomes true, the job state is updated to RUNNING. Later, startJob() sets the job state to SCHEDULED again before immediately transitioning it back to RUNNING, causing an unnecessary intermediate state change.

Does this PR introduce any user-facing change?

No.

How was this patch tested?

I believe the existing tests already cover this change.

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 necessary, please update incompatible-changes.md to describe the incompatibility caused by this PR.
• 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

[LiJie20190102]

Is this duplicated with #10133

[dybyte]

Yes, it is related, but I treated it as a separate concern from #10133.

[corgy-w]

After going through the details, I agree that such issues do exist.

[corgy-w]

Thanks for your contribution.

[corgy-w]

cc @zhangshenghang

[davidzollo]

+1