fix: preserve Gemini tool response function names

[Blueteemo]

Summary / 摘要

• Resolve opaque Gemini tool_call_id values back to their original function names when rebuilding conversation history.

• Preserve explicit name fields and the existing legacy fallback behavior.

• Add regression tests for opaque IDs and both fallback paths.

• 在重建 Gemini 对话历史时，将不透明的 tool_call_id 正确映射回原始函数名。

• 保留显式 name 字段及现有的旧格式回退行为。

• 为不透明 ID 和两条回退路径补充回归测试。

Problem / 问题

Gemini requires functionResponse.name to match the preceding functionCall.name. Existing history often stores only an opaque ID such as call_xxx, causing rebuilt requests to fail with HTTP 400.

Gemini 要求 functionResponse.name 与前面的 functionCall.name 一致。现有历史记录通常只保存 call_xxx 形式的不透明 ID，导致重建后的请求因名称不匹配而返回 HTTP 400。

Testing / 测试

• uv run ruff check astrbot/core/provider/sources/gemini_source.py tests/test_gemini_source.py
• uv run ruff format --check astrbot/core/provider/sources/gemini_source.py tests/test_gemini_source.py
• uv run pytest -q tests/test_gemini_source.py — 15 passed

Fixes #9876

Summary by Sourcery

Preserve Gemini function names when rebuilding tool responses so reconstructed conversations remain valid.

Bug Fixes:

• Preserve the original Gemini function name when reconstructing tool responses from opaque tool call IDs.
• Retain explicit tool response names and the legacy tool-call-ID fallback behavior.

Tests:

• Add regression coverage for opaque tool-call ID mapping and both tool-name fallback paths.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

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

• X
• Mastodon
• LinkedIn
• Facebook