docs: fix broken installation link in telegram bot tutorial

[NubsCarson]

Summary

All four language versions of the Telegram bot tutorial linked to ../getting-started/installation.md, but there is no getting-started/ directory under docs/. The canonical install page is docs/installation.mdx (plus per-locale docs/<lang>/installation.mdx), and other docs reference it via the Mintlify-style absolute path /installation (see e.g. docs/cli/overview.md:126, docs/what-you-can-build.md:173).

Each tutorial now points at the locale-appropriate absolute path:

• docs/guides/tutorial-telegram-bot.md → /installation
• docs/es/guides/tutorial-telegram-bot.md → /es/installation
• docs/fr/guides/tutorial-telegram-bot.md → /fr/installation
• docs/zh/guides/tutorial-telegram-bot.md → /zh/installation

All four target files exist on disk, so the links now resolve.

Test plan

• Verified docs/getting-started/ does not exist
• Verified docs/installation.mdx and docs/{es,fr,zh}/installation.mdx all exist
• Diff is 4 lines across 4 files, no behavioral changes

🤖 Generated with Claude Code

[github-actions]

All claims verified. The diff is minimal and correct. Here is my review:

---

1. Classification (derived): docs — consistent with author's claim

2. Rubric (derived): Verify the broken links actually point to non-existent paths, the replacement paths exist on disk, and that link style matches the pattern used elsewhere in the docs.

3. Scope verdict: in scope

4. Universal invariants: all intact — this PR touches only docs markdown files, none of the invariant-bearing source files.

5. Judgment:

• Needed? — OK: docs/getting-started/ does not exist; the old relative links were definitively broken.
• Better than existing? — OK: fixes a 404 → working link, no regression possible.
• Duplication? — OK
• Blast radius covered? — OK: all four locale variants updated consistently.
• Logic sound? — OK: verified all four target files (docs/installation.mdx, docs/es/installation.mdx, docs/fr/installation.mdx, docs/zh/installation.mdx) exist on disk. Absolute Mintlify-style paths match the pattern used elsewhere in the docs tree.
• Complexity appropriate? — OK: 4-line change, one fix per locale file.
• Tested meaningfully? — OK: N/A for a docs link fix; author verified file existence in test plan, confirmed correct.
• Matches conventions? — OK: consistent with how other docs reference /installation (e.g. docs/cli/overview.md:126, docs/what-you-can-build.md:173).
• Plausible breakage mode identified? — None credible. The only risk would be if Mintlify is configured differently per-locale, but absolute paths are the documented convention and /es/installation etc. resolve to confirmed files.

6. PR-type-specific checks (derived):

• Broken link claim verified: OK — docs/getting-started/ confirmed absent
• Replacement target files exist: OK — all four .mdx files confirmed on disk
• Link style matches existing docs convention: OK — matches absolute-path pattern used elsewhere
• All locale variants covered (en, es, fr, zh): OK
• No behavioral/code changes smuggled in: OK

7. Security: clear

8. Decision: APPROVE