docs(tools-reference): fix stale feishu_comment.py path

[santhiprakash]

What does this PR do?

Fixes a stale file path in the tools-reference documentation (English and Chinese locale mirrors).

The feishu_doc toolset description references gateway/platforms/feishu_comment.py, which no longer exists. The Feishu platform was migrated from gateway/platforms/ to plugins/platforms/ in PR #49408, so the correct path is plugins/platforms/feishu/feishu_comment.py.

Related Issue

Self-sourced docs drift found by path verification against the current main branch.

Type of Change

• 📝 Documentation update

Changes Made

• website/docs/reference/tools-reference.md (line 67): updated gateway/platforms/feishu_comment.py → plugins/platforms/feishu/feishu_comment.py
• website/i18n/zh-Hans/.../reference/tools-reference.md (line 67): same fix in the Chinese locale mirror

How to Test

1. git show plugins/platforms/feishu/feishu_comment.py — confirms the file exists at the new path
2. ls gateway/platforms/feishu_comment.py — confirms the old path does not exist
3. grep -r "gateway/platforms/feishu_comment" website/ — confirms no remaining stale references

Checklist

Code

• I've read the Contributing Guide
• My commit messages follow Conventional Commits
• I searched for existing PRs to make sure this isn't a duplicate
• My PR contains only changes related to this fix/feature (no unrelated commits)
• I've run pytest tests/ -q and all tests pass — N/A (docs-only)
• I've added tests for my changes — N/A (docs-only)

Documentation & Housekeeping

• I've updated relevant documentation (README, docs/, docstrings) — or N/A
• I've updated cli-config.yaml.example if I added/changed config keys — or N/A
• I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
• I've considered cross-platform impact (Windows, macOS) — or N/A
• I've updated tool descriptions/schemas if I changed tool behavior — or N/A

[santhiprakash]

Closing: target files were removed/restructured in upstream main. Will re-verify and re-ship against the new docs structure if the issue persists.