Lease PATCH generate wrong content-type

[leonardo-zup]

Describe the bug
Line 1917
kubernetes/src/main/java/io/kubernetes/client/openapi/apis/CoordinationV1Api.java

        final String[] localVarContentTypes = {
            "application/json"
        };

Client Version
25.0.0

Kubernetes Version
1.33

Java Version
Java 21

To Reproduce
Any call of .execute() after

    public APIpatchNamespacedLeaseRequest patchNamespacedLease(@jakarta.annotation.Nonnull String name, @jakarta.annotation.Nonnull String namespace, @jakarta.annotation.Nonnull V1Patch body) {
        return new APIpatchNamespacedLeaseRequest(name, namespace, body);
    }

KubeConfig
Not applicable.

Server (please complete the following information):
Not applicable – the Server does not affect this issue.

Additional context
Not applicable.

[brendandburns]

That code is auto-generated and Patch is non-standard from a RESTful point of view. Please use PatchUtils when performing patches.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten