fix: 忽略 Gemini “返回内容为空”的错误消息，将 OpenAI 和 Gemini 的此类消息以 info 级别输出在控制台上。

[MCjiaozi]

此 PR 与 #2279 同类

Motivation

#2279 仅解决了 OpenAI 提供商的此类问题，此 PR 解决 Gemini 的空消息返回问题。
未对其他供应商做出相应更改是因为尚未测试其他供应商的模型。

Modifications

• raise Exception("API 返回的内容为空。")改为logger.debug("API 可能返回了空消息。")，避免输出到消息平台
• 添加了logger.debug作为控制台提示。

Check

• 😊 我的 Commit Message 符合良好的规范
• 👀 我的更改经过良好的测试
• 🤓 我确保没有引入新依赖库，或者引入了新依赖库的同时将其添加到了 requirements.txt 和 pyproject.toml 文件相应位置。
• 😮 我的更改没有引入恶意代码

[sourcery-ai]

Hey @MCjiaozi - 我已经审阅了你的更改 - 以下是一些反馈：

• 空响应处理逻辑在不同提供者之间重复；考虑将其提取到共享的帮助函数中以避免冗余。
• 与其记录空的 result_parts 并继续执行，你可能希望提前返回一个空的 MessageChain 以提高清晰度。
• 考虑使用较低的日志级别 (debug) 或使空响应日志可配置，因为信息日志可能会使生产输出变得混乱。

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Empty response handling logic is duplicated across providers; consider extracting it into a shared helper to avoid redundancy.
- Rather than logging an empty `result_parts` and falling through, you may want to early-return an empty `MessageChain` for clarity.
- Consider using a lower log level (debug) or making the empty-response logs configurable, as info logs might clutter production output.

---

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.}

Original comment in English

Hey @MCjiaozi - I've reviewed your changes - here's some feedback:

• Empty response handling logic is duplicated across providers; consider extracting it into a shared helper to avoid redundancy.
• Rather than logging an empty result_parts and falling through, you may want to early-return an empty MessageChain for clarity.
• Consider using a lower log level (debug) or making the empty-response logs configurable, as info logs might clutter production output.

Prompt for AI Agents

Please address the comments from this code review:
## Overall Comments
- Empty response handling logic is duplicated across providers; consider extracting it into a shared helper to avoid redundancy.
- Rather than logging an empty `result_parts` and falling through, you may want to early-return an empty `MessageChain` for clarity.
- Consider using a lower log level (debug) or making the empty-response logs configurable, as info logs might clutter production output.

---

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.}