[BUG] V1NodeSystemInfo.kubeProxyVersion is incorrectly marked as @Nonnull after removal in K8s v1.33

Describe the bug
In Kubernetes v1.33, the status.nodeInfo.kubeProxyVersion field was officially removed (KEP-4004) because its value was not consistently accurate. However, in the generated Java client, the kubeProxyVersion field in V1NodeSystemInfo is still annotated with @jakarta.annotation.Nonnull.
This is highly unreasonable and causes issues when interacting with K8s v1.33+ clusters. Since the API no longer returns this field, it will be deserialized as null, which directly violates the @Nonnull contract and leads to potential NullPointerExceptions or validation failures in downstream applications relying on this client.

Client Version
25.0.x

Kubernetes Version
1.34

Java Version
Java 8

To Reproduce
Steps to reproduce the behavior:

Expected behavior
A clear and concise description of what you expected to happen.

KubeConfig
Not applicable. This is a model definition issue related to upstream API changes.

Server (please complete the following information):
OS: Linux
Environment: Container / Bare-metal
Cloud: N/A

Additional context
This issue stems from the deprecation and removal of status.nodeInfo.kubeProxyVersion in K8s v1.33 (KEP-4004). The code generator needs to be updated to reflect this upstream API change.

生成された V1NodeSystemInfo モデルから始め、その kubeProxyVersion アノテーションを、KEP-4004 で説明されている Kubernetes v1.33 API の変更と比較します。このフィールドを生成する原因となっている code-generator の入力を追跡し、削除されたフィールドが @Nonnull としてマークされないように生成済みクライアントを更新します。完了条件は、Kubernetes v1.33+ のレスポンスを nullability 契約に違反せずにデシリアライズできることです。