chore(mcp): release the SDK and yaml bumps that #69 left unpublished

[Viserion77]

Summary

• Adds the changeset chore(deps): bump the production-dependencies group across 1 directory with 6 updates #69 needed and Dependabot cannot write.
• chore(deps): bump the production-dependencies group across 1 directory with 6 updates #69 bumped two runtime dependencies of a published package —
  @treeui/mcp's @modelcontextprotocol/sdk (^1.17.4 → ^1.30.1) and
  yaml (^2.9.0 → ^2.9.1). Without a changeset the bump stops at main:
  the repository and the registry both say 0.8.0 while declaring different
  dependency ranges, so npm i @treeui/mcp still resolves the old SDK.
• Releases @treeui/mcp@0.8.1. No other package is touched.

Validation

• pnpm -w exec changeset status — only @treeui/mcp, at patch
• pnpm lint
• pnpm --filter @treeui/mcp test — 15 passing
• The real server, not just the unit suite. Thirteen minor versions of
  the SDK is too far to take on trust, so the server was driven over stdio:
  initialize completes on protocol 2024-11-05, and tools/list returns
  all six tools (search_components, recommend_components,
  get_component, get_setup_guide, search_recipes, search_tokens).

Notes

• Follow-up, unrelated to this bump but found while probing: the server reports
  serverInfo.version as catalog.packageVersion
  (packages/mcp/src/server.ts:143), which is @treeui/vue's version. A
  client sees @treeui/mcp v0.32.0 for a package that is 0.8.0. Informative,
  but serverInfo.version means the server's own version in the protocol.
• Worth considering: Dependabot cannot write changesets, so any future bump of a
  published package's runtime dependency lands with this same silent drift. A CI
  check that fails when packages/*/package.json dependencies change without a
  changeset would catch it at the PR instead of after the merge.