#19338: Create README_TR

Added Turkish Translation of the OpenClaw for Turkish Users. <!-- greptile_comment --> <h3>Greptile Summary</h3> This PR adds a Turkish translation of the main `README.md` as a new file `README_TR`. The translation is comprehensive (550 lines) and faithfully mirrors the structure and content of the original English README, including all badges, links, code blocks, configuration examples, and contributor avatars. - The file is missing the `.md` extension (`README_TR` instead of `README_TR.md`), so GitHub will not render it as Markdown — all formatting will appear as raw text. - The PR description template is completely unfilled — no summary, change type, or verification details are provided. - This is the first translated README in the repository. The existing i18n infrastructure (`docs/.i18n/`) is focused on the Mintlify docs site, not root-level READMEs, so there is no established convention for translated README files at the repo root. - The original `README.md` does not link to this translation, so discoverability may be limited. <h3>Confidence Score: 3/5</h3> - This is a documentation-only PR with no code changes, so it carries no runtime risk, but the file extension issue prevents the content from rendering properly. - The translation content appears faithful and the PR is docs-only with zero risk to functionality. However, the missing `.md` extension is a clear issue that would make the file unreadable on GitHub, and the empty PR description makes it harder to review the contributor's intent and testing approach. - `README_TR` — needs to be renamed to `README_TR.md` for proper Markdown rendering on GitHub. _{Last reviewed commit: 2b2e76d} <!-- greptile_other_comments_section --> _{(2/5) Greptile learns from your feedback when you react with thumbs up/down!} <!-- /greptile_comment -->