Create v2.10.0 docs version (missing after release)

[rootsongjc]

Problem

HAMi v2.10.0 was released on Aug 21, but docs:version v2.10.0 was never run. The site still serves v2.9.0 as the default at /docs, and the version dropdown has no v2.10.0 entry.

Steps

1. Merge these docs/ PRs first (otherwise their changes miss the v2.10.0 snapshot)

• docs(get-started): simplify quick start and online installation guides #712 docs(userguide): add component support tags to feature pages #713 docs(mthreads): fix device memory unit to 512 MiB and clarify sgpu-memory #708 docs(device): warn against Kubernetes quantity suffixes for device memory requests #714 docs(developers): add missing task dispatch section and diagram to protocol.md #811 (also backport to the v2.9.0 snapshot)
• docs(mig): document reservation-first Dynamic MIG #794 (v2.10 feature docs — highest priority)
• docs(scheduler): document per-pod scoring weights #759 docs: add hami_host_gpu_memory_controller_utilization_ratio to host metrics table #775 docs: audit supported devices matrix and clarify support status #684 docs(device-supported): add a component column per device with links #839 docs(nav): group the sidebar into a guided path and make the devices matrix the vendor index #838 docs(get-started): add a page for choosing between HAMi, HAMi-DRA, Volcano vGPU and KAI #837 docs: update NVIDIA registration format #835 docs: fix device registration handshake #822 docs: clarify AWS Marketplace version #828 docs: improve grammar and clarity in online installation guide #815 doc: update range grammar description in GPU virtualization #792

2. Cut the version

npm run docusaurus docs:version v2.10.0

Then edit i18n/zh/docusaurus-plugin-content-docs/version-v2.10.0.json and change the label from "下一个" to v2.10.0.

3. Verify

Run npm run build and confirm the version dropdown shows Next / v2.10.0 / v2.9.0 in both en and zh.