[Refactor/Chore] API Machinery: Migrate API endpoints to layered application services

### 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] This is only for refactors or chores; if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general).
- [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] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
- [x] Please do not modify this template :) and fill in all the required fields.

### Description

Migrate Dify API endpoints toward layered application services, using [#39822](https://github.com/langgenius/dify/pull/39822) as the initial reference implementation.
The goal is to make API dependencies, business boundaries, database access, and side effects explicit while preserving existing behavior unless an API contract change is intentionally approved.
This is an umbrella issue for the complete API Machinery migration. Individual controller/resource families can be claimed and implemented through separate PRs.

### Motivation

_No response_

### Additional Context

_No response_