feat: add xiaomi MiMo TTS & STT providers

[RichardLiuda]

为 AstrBot 增加 MiMo STT / TTS 提供商支持，并补充 Dashboard 中 MiMo 配置项的展示文案。

本 PR 对齐以下 issue 的需求：

• Resolves [Feature]新增模型供应商小米 #6592
• Resolves [Bug]MiMo-V2-TTS、MiMo-V2-Omni模型无法被正确设置为语音合成/语音识别提供商 #6594

本次改动同时支持：

• 使用 mimo-v2-omni 作为语音转文字（STT）提供商
• 使用 mimo-v2-tts 作为文字转语音（TTS）提供商

同时补充了 Dashboard 中新增 MiMo 配置项的说明文案，提升配置可读性。

Modifications / 改动点

• 在 astrbot/core/config/default.py 中新增 MiMo STT(API) provider 模板
• 在 astrbot/core/config/default.py 中保留并完善 MiMo TTS(API) provider 模板
• 在 astrbot/core/provider/manager.py 中注册 mimo_stt_api 和 mimo_tts_api
• 新增 astrbot/core/provider/sources/mimo_api_common.py，抽取 MiMo 公共默认值与请求辅助逻辑
• 新增 astrbot/core/provider/sources/mimo_stt_api_source.py，实现 MiMo STT provider
• 调整 astrbot/core/provider/sources/mimo_tts_api_source.py，复用 MiMo 公共逻辑并完善异常处理
• 在 dashboard/src/composables/useProviderSources.ts 中补充 MiMo STT provider 类型映射
• 为 MiMo STT 配置项补充 Dashboard 元数据说明：
  • mimo-stt-system-prompt
  • mimo-stt-user-prompt
• 为 MiMo TTS 配置项补充 Dashboard 元数据说明：
  • mimo-tts-voice
  • mimo-tts-format
  • mimo-tts-style-prompt
  • mimo-tts-dialect
  • mimo-tts-seed-text
• 在以下多语言文件中补充 MiMo 配置项文案：
  • zh-CN
  • en-US
  • ru-RU
• 新增 tests/test_mimo_api_sources.py，覆盖 MiMo STT / TTS 的请求构造与错误处理场景

与官方文档对齐 / Official API Alignment

本实现对齐了 MiMo OpenAI 兼容接口文档：

• https://platform.xiaomimimo.com/#/docs/api/chat/openai-api

对齐内容包括：

• 使用 OpenAI 兼容的 /v1/chat/completions 接口
• 使用单一 Authorization: Bearer <MIMO_API_KEY> 鉴权方式
• 默认使用 mimo-v2-omni 作为 STT 模型，mimo-v2-tts 作为 TTS 模型
• 按文档要求传递 input_audio.data
• 支持文档中说明的 MiMo TTS voice、format 等参数

Compatibility / 兼容性说明

• This is NOT a breaking change. / 这不是一个破坏性变更。

Screenshots or Test Results / 运行截图或测试结果

验证步骤：

1. 启动 AstrBot 后端

   uv run main.py

2. 启动 Dashboard 开发环境

   cd dashboard
   pnpm dev

3. 打开 Provider 页面并确认：

   • MiMo STT(API) 出现在语音转文字提供商列表中
   • MiMo TTS(API) 出现在文字转语音提供商列表中
   • MiMo STT / TTS 新增配置项可以正常显示，并带有对应说明文案

本地检查结果：

uv run ruff format .
uv run ruff check .
uv run pytest tests/test_mimo_api_sources.py
python3 -m py_compile astrbot/core/config/default.py astrbot/core/provider/manager.py astrbot/core/provider/sources/mimo_api_common.py astrbot/core/provider/sources/mimo_stt_api_source.py astrbot/core/provider/sources/mimo_tts_api_source.py

以上检查均已通过。

运行效果：

Checklist / 检查清单

• 😊 If there are new features added in the PR, I have discussed it with the authors through issues/emails, etc.
  / 如果 PR 中有新加入的功能，已经通过 Issue / 邮件等方式和作者讨论过。

• 👀 My changes have been well-tested, and "Verification Steps" and "Screenshots" have been provided above.
  / 我的更改经过了良好的测试，并已在上方提供了“验证步骤”和“运行截图”。

• 🤓 I have ensured that no new dependencies are introduced, OR if new dependencies are introduced, they have been added to the appropriate locations in requirements.txt and pyproject.toml.
  / 我确保没有引入新依赖库，或者引入了新依赖库的同时将其添加到 requirements.txt 和 pyproject.toml 文件相应位置。

• 😮 My changes do not introduce malicious code.
  / 我的更改没有引入恶意代码。

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

此拉取请求为 AstrBot 引入了 MiMo TTS 提供商支持，解决了用户无法直接使用 MiMo TTS 进行文本转语音的问题。同时，它还补充了 Dashboard 中相应配置项的展示文案，确保新增的配置项拥有清晰的说明，从而提升了用户体验和系统的可扩展性。

Highlights

• MiMo TTS 提供商支持: 在 astrbot/core/config/default.py 中新增了 MiMo TTS(API) 提供商模板，并补充了相关配置项的元数据定义。
• 后端集成: 在 astrbot/core/provider/manager.py 中注册了 mimo_tts_api，并新增了 astrbot/core/provider/sources/mimo_tts_api_source.py 文件以实现 MiMo TTS 提供商的逻辑。
• 前端 Dashboard 更新: 在 dashboard/src/composables/useProviderSources.ts 中补充了 MiMo TTS 提供商类型映射，并在 dashboard/src/utils/providerUtils.js 中添加了 MiMo 提供商图标。
• 多语言支持: 在 dashboard/src/i18n/locales/zh-CN/features/config-metadata.json、en-US/features/config-metadata.json 和 ru-RU/features/config-metadata.json 等多语言文件中补充了 MiMo TTS 配置项的说明文案。

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• Consider extracting the MiMo-specific defaults (base URL, default model, default voice, seed text) into module-level constants or config so they’re easier to update and reuse without hunting through the provider implementation.
• The error handling in get_audio currently raises generic Exception; using a more specific custom exception type (or reusing an existing provider error type) would make it easier for callers to distinguish MiMo TTS failures from other unexpected errors.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider extracting the MiMo-specific defaults (base URL, default model, default voice, seed text) into module-level constants or config so they’re easier to update and reuse without hunting through the provider implementation.
- The error handling in `get_audio` currently raises generic `Exception`; using a more specific custom exception type (or reusing an existing provider error type) would make it easier for callers to distinguish MiMo TTS failures from other unexpected errors.

## Individual Comments

### Comment 1
<location path="astrbot/core/provider/sources/mimo_tts_api_source.py" line_range="135-136" />
<code_context>
+            ) from exc
+
+        data = response.json()
+        audio_data = (
+            data.get("choices", [{}])[0].get("message", {}).get("audio", {}).get("data")
+        )
+        if not audio_data:
</code_context>
<issue_to_address>
**issue:** Indexing into `choices[0]` can raise when the API returns an empty list, leading to an uncaught error path.

If MiMo returns `{"choices": []}` (or omits it but sets it to an empty list), `data.get("choices", [{}])[0]` raises `IndexError` before your `if not audio_data` guard runs. Consider handling the empty-list case explicitly, e.g.:

```python
choices = data.get("choices") or []
first_choice = choices[0] if choices else {}
message = first_choice.get("message", {})
audio_data = message.get("audio", {}).get("data")
```

This keeps failures within your explicit checks and avoids a surprising `IndexError`.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

此拉取请求成功地为 AstrBot 添加了 MiMo TTS 提供商支持，并更新了 Dashboard 中的相关配置项和多语言文案。代码结构清晰，遵循了现有提供商的实现模式。我发现了一些可以改进的地方，主要集中在 MiMo TTS API 源文件的逻辑和类型提示上，这些改进将提高代码的健壮性和可维护性。

[gemini-code-assist]

当前 _build_user_prompt 方法的逻辑可能导致 seed_text 被重复添加。如果 style_prompt 或 dialect 存在，prompt_parts 将不为空，然后 seed_text 会再次被追加。这可能不是预期行为。

建议修改逻辑，确保 seed_text 只在 prompt_parts 为空时作为默认值返回，或者只在 prompt_parts 不为空时追加一次。

Suggested change

	if not prompt_parts:
	return self.seed_text
	if self.seed_text.strip():
	prompt_parts.append(self.seed_text.strip())
	if not prompt_parts:
	return self.seed_text
	# 如果 prompt_parts 不为空，且 seed_text 存在，则追加 seed_text
	if self.seed_text.strip() and prompt_parts:
	prompt_parts.append(self.seed_text.strip())
	return " ".join(prompt_parts)

[gemini-code-assist]

在 build_headers 函数中，同时设置 api-key 和 Authorization 头部可能存在冗余。通常情况下，API 只会使用其中一个进行认证。建议查阅 MiMo TTS API 的官方文档，确认只需要其中一个头部，以避免潜在的冲突或不必要的请求开销。

Suggested change

	if api_key:
	headers["api-key"] = api_key
	headers["Authorization"] = f"Bearer {api_key}"
	if api_key:
	# 根据 MiMo API 文档，可能只需要其中一个头部
	# 例如，如果只需要 Authorization 头部：
	headers["Authorization"] = f"Bearer {api_key}"
	# 如果只需要 api-key 头部：
	# headers["api-key"] = api_key

[gemini-code-assist]

在 create_http_client 函数中，client_kwargs 的类型提示 dict[str, object] 过于宽泛。考虑到 timeout 和 follow_redirects 的具体类型，可以将其细化为 dict[str, int | bool | str]，以提高类型安全性。

Suggested change

	def create_http_client(timeout: int | None, proxy: str) -> httpx.AsyncClient:
	def create_http_client(timeout: int | None, proxy: str) -> httpx.AsyncClient:
	client_kwargs: dict[str, int | bool | str] = {