refactor: rename project from TuyaOpenClaw to TClaw

[maidang-xing]

Renames the project from TuyaOpenClaw to TClaw across docs, skills docs, code, comments, file names, GitHub Actions and links.

Mapping

Old	New	Where
TuyaOpenClaw	TClaw	prose, doc titles, workflow names, repo URLs
TUYAOPEN_CLAW	TCLAW	agent/Kconfig symbols
TUYAOPENCLAW	TCLAW	root Kconfig symbols, TCLAW_DEVICE_ID
tuyaopen_claw	tclaw	source file names, function names
tuyaopenclaw	tclaw	device-id default, doc-site slugs

File renames:

• include/tuyaopen_claw_chat.h → include/tclaw_chat.h
• src/tuyaopen_claw_chat.c → src/tclaw_chat.c

Kconfig symbols (definitions and every CONFIG_ consumer moved together):
TCLAW_USE_AI_COMPONENTS, TCLAW_USE_EXT_RAM, TCLAW_AGENT_STACK,
TCLAW_CONTEXT_BUF_SIZE, TCLAW_HISTORY_MAX_COUNT.

Doc links now point at tuyaopen.ai/docs/tclaw/* — this also unified two
previously divergent slugs (README used docs/duckyclaw/, the Lua doc used
docs/tuyaopenclaw/). The matching doc-site change is in
Tuya-Community/TuyaOpen.io.

Verification

• Provably a pure rename. For all 51 changed files, applying the mapping
  above to the pre-rename original reproduces this branch exactly
  (whitespace-normalized). The only content edits beyond the mapping are the
  two README "Philosophy" paragraphs, which decomposed the old name and no
  longer parsed after it changed.
• Clean T5AI build passes: tos.py clean -f && tos.py build → exit 0.
• Kconfig plumbing intact: the build generates TCLAW_AGENT_STACK 24576,
  TCLAW_CONTEXT_BUF_SIZE 32768, TCLAW_HISTORY_MAX_COUNT 10,
  TCLAW_USE_AI_COMPONENTS 1, TCLAW_USE_EXT_RAM 1 — the same values as
  before the rename — and no stale old-name key remains in the generated
  config.
• The TuyaOpen/ SDK submodule contains zero references to the renamed
  symbols and its pointer is untouched.

Deliberately left alone

• The contrib.rocks contributor image URL keeps repo=tuya/TuyaOpenClaw
  (image links were out of scope; the GitHub repo is still named
  TuyaOpenClaw today, so the badge keeps working).
• All DuckyClaw / Ducky mascot references.

Needs a maintainer action before merge is fully effective

release.yml and sync-to-gitee.yml are now gated on
github.repository == 'tuya/TClaw' and push to tuya-open/TClaw. Until the
GitHub repo is renamed to tuya/TClaw and the Gitee mirror is renamed, those
jobs will silently skip (the if: is simply false — no error surfaces).
check-build.yml has no repo gate, so PR builds are unaffected either way.

Two smaller items worth a maintainer's call, both pre-existing contracts that
this rename changes the value of:

• gateway/acp_client.c sends "deviceFamily": "TClaw" in the ACP connect
  handshake. This field was "DuckyClaw" historically and already survived one
  rename, and the real client identity is id: "openclaw-control-ui"
  (unchanged), so it looks informational — but confirm the gateway doesn't key
  off it.
• TCLAW_DEVICE_ID default is now "tclaw-001". Provisioned devices read KV
  app.device_id first and are unaffected; only unprovisioned devices report a
  different displayName.

🤖 Generated with Claude Code

---

Also in this PR: TuyaOpen submodule bumped to latest master

Fast-forwards the SDK 50 commits, v1.8.0-14-g4e6d0e7e → v1.9.0-36-ge82840dc.
This is an unrelated change riding along with the rename — happy to split it into
its own PR if you'd rather review them separately.

Verified on this branch:

• Clean T5AI build passes (tos.py clean -f && tos.py build → exit 0), with the
  renamed src/tclaw_chat.c compiling into the app.
• The five TCLAW_* Kconfig macros still generate the same values under the new
  SDK (24576 / 32768 / 10 / 1 / 1), so the rename and the bump don't interact.
• None of the four files this app overlays into ai_components
  (ai_agent.{c,h}, ai_mcp_server.{c,h}) changed upstream across the bump, so
  overlay/ is not silently masking a new upstream fix.

⚠️ Heads-up for anyone building this branch: the new SDK pins a different
T5AI platform commit (13379b63, was 29fcfd3d). tos.py build stops on an
interactive prompt asking to update the platform — answer y (or run with the
prompt suppressed) or the build aborts. Worth confirming CI handles that prompt
non-interactively.