docs: Add Turkish (tr) translation of documentation

[system-conf]

docs: Add Turkish (tr) translation of documentation

Summary

I'd like to contribute a Turkish translation of the project documentation to make chrome-devtools-mcp more accessible to the Turkish-speaking developer community.

Motivation

• The Turkish developer community is growing rapidly, and many developers benefit from documentation in their native language.
• Several popular open-source projects (e.g., React, Vue, Node.js) already maintain translated documentation.
• Translating docs lowers the barrier to entry for Turkish-speaking developers who want to use and contribute to this project.

Proposed Approach

I'd like to get maintainer feedback on the preferred structure before starting the work. Here are the options I considered:

Option A: docs/tr/ subdirectory (preferred)

Create translated versions of each doc file under docs/tr/:

docs/
  tr/
    README.tr.md
    cli.md
    troubleshooting.md
    tool-reference.md
    design-principles.md
    slim-tool-reference.md
    debugging-android.md

• Add a language switcher link at the top of each original doc file (e.g., [Türkçe](tr/cli.md))
• Add corresponding link back from translated files (e.g., [English](../cli.md))

Option B: Root-level README.tr.md only

A single translated README file at the repository root, similar to how some projects handle translations.

Option C: Separate repository

Maintain translations in a separate fork/repo. This keeps the main repo clean but reduces visibility.

Scope

If Option A is approved, I plan to translate:

1. README.md → docs/tr/README.tr.md
2. docs/cli.md → docs/tr/cli.md
3. docs/troubleshooting.md → docs/tr/troubleshooting.md
4. docs/design-principles.md → docs/tr/design-principles.md
5. docs/tool-reference.md → docs/tr/tool-reference.md
6. docs/slim-tool-reference.md → docs/tr/slim-tool-reference.md
7. docs/debugging-android.md → docs/tr/debugging-android.md

Notes

• Code blocks, command names, and tool names will remain in English (only prose/descriptions translated).
• I'm happy to maintain the translations and keep them up-to-date with future changes.
• I will sign the Google CLA before submitting the PR.

Questions for maintainers

1. Do you welcome documentation translations in this repo?
2. Which structure do you prefer (A, B, or C)?
3. Should translated docs be kept in sync via CI checks, or manually?
4. Any concerns about maintenance burden for translated docs?

---

Thanks for considering this contribution! 🙏