feat(auth): implement Alibaba Cloud Standard API Key support

[JohnKeating1997]

TLDR

• Adds a dedicated Alibaba Cloud Standard API Key setup path inside /auth under the API Key level, while keeping the top-level menu as Qwen OAuth / Alibaba Cloud Coding Plan / API Key.
• Lets users choose region-specific DashScope compatible endpoints, input API key, and then input model ID in one guided flow.
• Persists credentials to env.DASHSCOPE_API_KEY and writes/updates modelProviders.openai + model.name, reducing manual settings edits for standard DashScope users.

Screenshots / Video Demo

Dive Deeper

• Added Alibaba standard API key constants in packages/cli/src/constants/alibabaStandardApiKey.ts.
• Extended auth action plumbing with handleAlibabaStandardSubmit through useAuth, AppContainer, and UIActionsContext.
• Implemented guided flow in AuthDialog:
  • API Key -> Select API Key type
  • Alibaba Cloud Standard API Key -> region select -> API key input -> model ID input
  • Custom API Key keeps existing custom-config guidance page
• Region endpoints covered in this change:
  • North China 2 (Beijing): [https://dashscope.aliyuncs.com/compatible-mode/v1](https://dashscope.aliyuncs.com/compatible-mode/v1%60)
  • Singapore: [https://dashscope-intl.aliyuncs.com/compatible-mode/v1](https://dashscope-intl.aliyuncs.com/compatible-mode/v1%60)
  • US (Virginia): [https://dashscope-us.aliyuncs.com/compatible-mode/v1](https://dashscope-us.aliyuncs.com/compatible-mode/v1%60)
  • China (Hong Kong): [https://cn-hongkong.dashscope.aliyuncs.com/compatible-mode/v1](https://cn-hongkong.dashscope.aliyuncs.com/compatible-mode/v1%60)
• Duplicate model ID behavior remains first-entry-wins in model registry; this PR does not alter registry conflict semantics.

Reviewer Test Plan

1. Checkout this branch and run:
   • npm install
   • npm run build --workspace=packages/cli
   • npm start
2. In CLI, run /auth and verify top-level menu has:
   • Qwen OAuth
   • Alibaba Cloud Coding Plan
   • API Key
3. Select API Key and verify second-level menu:
   • Alibaba Cloud Standard API Key
   • Custom API Key
4. Select Alibaba Cloud Standard API Key and verify region list and endpoint text for each option.
5. Complete Standard flow:
   • input API key
   • input model ID (e.g. qwen3.5-plus)
6. Verify settings persistence:
   • env.DASHSCOPE_API_KEY is set
   • modelProviders.openai contains the selected model/baseUrl/envKey
   • security.auth.selectedType is openai
   • model.name matches entered model ID
7. Re-open /auth and verify behavior still navigates correctly and Esc back navigation works across nested steps.

Testing Matrix

	🍏	🪟	🐧
npm run	✅	❓	❓
npx	❓	❓	❓
Docker	❓	❓	❓
Podman	❓	-	-
Seatbelt	❓	-	-

Linked issues / bugs

Resolves #2664

[pomelo-nwu]

@JohnKeating1997 Thanks for your contribution！

[pomelo-nwu]

LGTM