docs(i18n): add Korean translations for remaining sections

[erishforG]

Summary

• Add Korean translations for the 3 remaining untranslated documentation sections
• Completes full Korean (ko) documentation coverage across all sections

New translations (10 files)

Section	Files
ko/provisioning/	kubernetes.mdx
ko/api-references/	index.mdx, metadata.mdx, mutation.mdx, query.mdx
ko/community/	contributing.mdx, development.mdx, governance.mdx, releases.mdx, roadmap.mdx

Translation quality

• Glossary terms applied consistently (엣지, 레이블, 별칭, 스키마, 인덱스, 쿼리, 뮤테이션, etc.)
• English terms preserved where required (Actionbase, HBase, Kafka, Kubernetes, Docker, CLI, API, etc.)
• Line-by-line structural match with English originals (all 10 files have identical line counts)
• All 93 internal/external links verified valid
• Code blocks preserved exactly; only comments translated
• MDX components (<Aside>, <Badge>, <LinkCard>) preserved exactly
• Formal polite tone (합니다/입니다) consistent with existing Korean translations

Test plan

• Verify Korean pages render correctly on the documentation site
• Check sidebar navigation includes new sections under Korean locale
• Confirm internal links between Korean pages work correctly
• Review translation accuracy for technical terminology

[CLAassistant]

All committers have signed the CLA.

[em3s]

The documentation and translation guide wasn't fully ready—our oversight. Since the content here is important, I'll handle the CI-related changes myself. We'll update the contribution guide later to cover this. Thanks! @erishforG

[erishforG]

@em3s

Thanks for the quick feedback, @em3s. All checks are green now. Whether you'd like to prepare the contribution guide first or merge the documentation and translation as-is, it's up to you.

[em3s]

@zipdoki @eazyhozy

We need an i18n review process. i18n Ally looks promising, but our current structure (root for en, /ko for Korean) may not work well with it.

For now, a simple script works:

# review.sh
#!/bin/bash
code -r "src/content/docs/$1" "src/content/docs/ko/$1"

Usage: ./review.sh introduction.mdx

Moving to /en and /ko structure is worth discussing separately. Will add to the contribution guide.

---

@erishforG

Our review process isn't fully set up yet, so this may take a bit longer. Working on it—thanks for your patience!