#19580: docs(tr): add Turkish FAQ starter page

## Summary This PR adds a Turkish FAQ starter page for OpenClaw documentation. ## Why Turkish-speaking users need a quick troubleshooting/reference page during onboarding and first runs. ## Scope - Added docs/tr-TR/help/faq.md - Includes a translated starter structure with key first-run diagnostics and common troubleshooting flows - Keeps English source untouched ## Notes - This is intentionally a starter/phase-1 FAQ translation. - Follow-up PRs can expand coverage section by section from docs/help/faq.md. <!-- greptile_comment --> <h3>Greptile Summary</h3> Adds a Turkish (`tr-TR`) FAQ starter page covering essential troubleshooting and first-run diagnostics. The file provides a condensed translation of key sections from the English FAQ, including a 60-second checklist, quick setup guidance, gateway connection troubleshooting, and model authentication basics. The translation is accurate and uses appropriate technical terminology. The structure follows Mintlify doc conventions with proper frontmatter and root-relative internal links. The author clearly notes this is a phase-1 translation with plans to expand coverage in follow-up PRs. Minor observation: Unlike the Chinese (`zh-CN`) FAQ which is auto-generated via `scripts/docs-i18n` and includes `x-i18n` metadata, this Turkish translation appears to be manually created. The AGENTS.md guidelines indicate `docs/zh-CN/**` is generated and shouldn't be edited manually, but there's no mention of Turkish translations following the same pipeline. <h3>Confidence Score: 5/5</h3> - This PR is safe to merge with no risk - This is a documentation-only change that adds a new localized file without modifying any existing code or documentation. The Turkish translation is accurate, follows the established documentation structure, and includes proper metadata. The file is properly placed in `docs/tr-TR/help/` following the repository's i18n directory conventions. - No files require special attention _{Last reviewed commit: d898a09} <!-- greptile_other_comments_section --> _{(3/5) Reply to the agent's comments like "Can you suggest a fix for this @greptileai?" or ask follow-up questions!} <!-- /greptile_comment -->