Workflow application management MCP support

### Self Checks

- [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542).
- [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones.
- [x] I confirm that I am using English to submit this report, otherwise it will be closed.
- [x] Please do not modify this template :) and fill in all the required fields.

### 1. Is this request related to a challenge you're experiencing? Tell me about your story.

At present, we are using self hosted version 1.7.0, and many online workflows are created previously. The working method is to update the workflow yml file through codex and claude code, and then import it into the online workflow application. The whole process is very complicated, and we hope to support the MCP service on the application management side. This way, we can link dify through client links such as codex and claude code to update workflows, view logs, create workflows, and other capabilities. For example, the MCP provided by n8n's official service itself

### 2. Additional context or comments

_No response_

### 3. Can you help us with this feature?

- [x] I am interested in contributing to this feature.

No implementation files, tests, or entry points are named. Start by locating the existing workflow YAML import and application-management interfaces, then determine the MCP operations needed for workflow updates, log viewing, and workflow creation; done means these capabilities work through client links such as Codex and Claude Code.

Written by the indexing model from the issue text.