[AIT-73302] Align ACP 4.4 version and upgrade documentation

[chinameok]

Summary

• Add the ACP 4.4 Kubernetes minor support contract: cluster creation on Kubernetes 1.35 and Compatible Versions 1.35 through 1.32.
• Document patch-specific CVO upgrade eligibility: ACP 4.1, 4.2, and 4.3 are inside the n-3 minor window, but each source patch must use a target exposed by availableUpdates and accepted by VersionUpgradePath; ACP 4.0 requires platform-provided intermediate hops.
• Keep the product-tested third-party Kubernetes onboarding range in the Kubernetes Support Matrix as one shared range for ACP 4.3 and later applicable releases.
• Align HCP, Traditional OS, Alauda OS, Global DR, Extension lifecycle, and upgrade guidance with their actual support boundaries.

Documentation boundaries

• Keep Kubernetes support at minor level in acp-docs; do not publish an exact Kubernetes build such as 1.35.6.
• Do not publish an exact containerd version in the ACP minor-release documentation.
• If a later ACP 4.4.x patch adds another Kubernetes minor, update the existing 4.4 matrix row instead of creating patch-specific documentation.
• Keep the Kubernetes Support Matrix as the single numerical source for current creation, Compatible Versions, and third-party onboarding ranges.
• Keep stable logic release-neutral. Retain version numbers only for real historical or support boundaries, such as CVO starting with ACP 4.3 and the ACP 4.0 to 4.4 intermediate-upgrade requirement.
• Patch-specific Alauda OS, Kubernetes build, containerd, CoreDNS, etcd, pause, and Kube-OVN values remain owned by the Immutable Infrastructure OS Support Matrix after release artifacts are available.

Review follow-up

• Remove the unverified Default Extend Baseline instead of presenting unsupported combinations as a support matrix.
• Keep the complete HCP boundary in the HCP overview and link to it from other overview pages.
• Generalize node readiness to ACP 4.4 or later and Kubernetes 1.35 or later when the target release reports an administrator gate; use the actual key from admin-gates.
• Route Traditional OS and Alauda OS Global DR procedures without enumerating infrastructure providers.
• Remove the internal Kubernetes 1.19 onboarding threshold from public documentation; publish only the product-tested range.

Exclusions

• Bare Metal scope is excluded and remains tracked separately.

Validation

• git diff --check
• yarn lint
• yarn build
• Full-text assertions for the 1.19 onboarding threshold, duplicate third-party range values, stale ACP 4.4 qualifiers, provider enumeration, readiness wording, and Default Extend Baseline

[cloudflare-workers-and-pages]

Deploying alauda-container-platform with    Cloudflare Pages

Latest commit:	e8a09c8
Status:	✅  Deploy successful!
Preview URL:	https://7cbfd860.alauda-container-platform.pages.dev
Branch Preview URL:	https://chao-ait-73302-acp-44-doc-al.alauda-container-platform.pages.dev

View logs