Proposal: migrate the existing DashScope provider to QwenCloud branding with compatibility #2129

Context

QwenCloud is the current AI model platform for international Qwen developers. MetaGPT already has a DashScope provider path in its provider registry.

Proposal

We would like to update the user-facing provider experience to QwenCloud without breaking existing api_type, provider registry entries, environment variables, endpoints, or saved configurations.

Would the maintainers prefer a display-name and documentation update, a QwenCloud alias that reuses the existing implementation, or a separate provider only where endpoint behavior differs?

Official references

• Website: https://www.qwencloud.com/
• API keys: https://home.qwencloud.com/api-keys
• Developer docs: https://docs.qwencloud.com/developer-guides/getting-started/introduction
• Models: https://www.qwencloud.com/models

The QwenCloud team can provide compatibility mapping, approved copy, model recommendations, and test support after the preferred migration path is confirmed.

QwenCloud contact: Jialing / QwenCloud Product Manager / https://github.com/evelyn-jialin-zhang