[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.

Commencez par le modèle V1NodeSystemInfo généré et comparez son annotation kubeProxyVersion avec la modification de l’API Kubernetes v1.33 décrite dans KEP-4004. Suivez l’entrée de code-generator responsable de ce champ et mettez à jour le client généré afin que le champ supprimé ne soit pas marqué comme @Nonnull. La tâche est terminée lorsque les réponses de Kubernetes v1.33+ peuvent être désérialisées sans violer le contrat de nullabilité.

Rédigé par le modèle d'indexation à partir du texte de l'issue.