[Feature][python] Find a good way to combine python api and UI

### Search before asking

- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.

### Description

**How to combine UI and codes when define and change workflow**: We could update workflow define by UI or by edit Python API code after we create it, and how to combine them. If would cause consistency issues when we create workflow by python api but change them in UI, cause UI modify directly change database metadata but python api do not know and still in the old version. **In python api define way, python file just like template, it parse the code and persist to database**

### Use case

_No response_

### Related issues

_No response_

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

No files, tests, or entry points are named. Start by examining the Python API workflow definition path, the UI workflow-editing path, and the database metadata they both update. Define how template parsing, version consistency, and UI/API changes should interact before proposing implementation work.

Written by the indexing model from the issue text.