[ko] Translate /team into Korean #879

Goal

Provide the Korean version of /team at /ko/team. This issue covers only this page.

English source

• apps/landing/src/app/(detail)/team/page.mdx

Files to add or update

• apps/landing/src/app/(detail)/team/page.ko.mdx
• apps/landing/src/i18n/pages.ts

Work

Copy the English page.mdx to page.ko.mdx in the same directory and translate it. Preserve imports and JSX structure. Update the metadata title/description, canonical to /ko/team and language alternatives for the English and Korean URLs. Register /team in apps/landing/src/i18n/pages.ts with a lazy import of the translated page. Follow the existing /docs/overview entry. Reuse the English layout directly; no Korean directory or layout wrapper is needed. Use the existing team layout in the map entry.

Getting started

This is intended for a first-time contributor. Comment to claim this page before starting, and send one focused PR. Questions are welcome.

Prerequisite: #881. Wait for that infrastructure to merge before submitting the translation. Context: #584.

Read the translation guide and use the Korean overview at apps/landing/src/app/(detail)/docs/overview/page.ko.mdx as an example. English stays at the original URL; untranslated /ko URLs automatically redirect to their English page.

Acceptance checklist

• Translate the complete assigned scope into natural Korean, including headings, prose, table descriptions and metadata.
• Keep API/package names, code behavior, numeric data, external links and benchmark caveats unchanged. Explanatory code comments may be translated.
• Preserve MDX imports and JSX structure. Fix relative imports when moving files; prefer @/ imports.
• Keep internal links root-relative (for example /docs/installation); locale-aware navigation adds /ko automatically.
• Verify both English and Korean URLs, mobile and desktop, links, tables and code blocks.
• From the repository root run bun install and bun run build; from apps/landing run bun dev and bun run build. Run node script.js to refresh search data; translated pages are connected explicitly in src/i18n/pages.ts. Run the type, lint and i18n checks listed in the translation guide.
• Register the translated page in src/i18n/pages.ts and verify that its /ko URL renders the translation instead of redirecting.
• Keep the English copy unchanged. Do not translate other pages in this PR.