feat(goreleaser): add version ldflags for kubectl build

[l-qing]

• Add version information ldflags for component-base
• Add version information ldflags for client-go
• Ensure version info is embedded in kubectl binary

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR is related to:

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[kiloconnect]

✅ No Issues Found - Re-reviewed

1 files reviewed | Confidence: 95% | Recommendation: Merge

Review Details

Files: .goreleaser-alauda.yml

Checked: Security, bugs, performance, error handling, version embedding patterns

Analysis: The PR successfully adds version ldflags for kubectl builds that follow established Kubernetes ecosystem patterns. The changes embed version information from both k8s.io/component-base/version and k8s.io/client-go/pkg/version packages, which are the standard packages used across Kubernetes-related projects for version information. The ldflags format is correct and the implementation aligns with Go build best practices.

Re-review Confirmation: Confirmed that the ldflags match exactly with those defined in hack/lib/version.sh (lines 158-161), both version packages exist and are widely used throughout the codebase, and kubectl already imports and uses the component-base version package. No issues found.