### What happened?

Aggregated API backend:  Call to `CREATE` endpoint consults `PATCH` field validation properties, even if the resource does not support the `PATCH` verb..

### What did you expect to happen?

Expected `CREATE` to be called with `CREATE` field validation without looking at the `PATCH` endpoint.

### How can we reproduce it (as minimally and precisely as possible)?

Create Open API v3 specification with a field validator.  Storage for API server (aggregated API server) advertises support only for `CREATE`, `GET`, `DELETE`

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.28.9
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.9-gke.1000000
```

</details>


### Cloud provider

<details>
GKE
</details>


### OS version

<details>

    architecture: amd64
    bootID: f993a6ef-ee9e-457b-856e-bfd51f9cdd22
    containerRuntimeVersion: containerd://1.7.13
    kernelVersion: 5.15.0-1054-gke
    kubeProxyVersion: v1.27.12-gke.1190000
    kubeletVersion: v1.27.12-gke.1190000
    machineID: 4da31cf9d84cf8d82e680abcb09130ae
    operatingSystem: linux
    osImage: Ubuntu 22.04.4 LTS
    systemUUID: 4da31cf9-d84c-f8d8-2e68-0abcb09130ae

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

Open API v3 requirement for `PATCH` verb support (introduced PR #115119)
This is a GitHub Issue
repo:kubernetes
owner:kubernetes
Title : Open API v3 requirement for `PATCH` verb support (introduced PR #115119)
Issue date:

--- start body ---
### What happened?

Aggregated API backend:  Call to `CREATE` endpoint consults `PATCH` field validation properties, even if the resource does not support the `PATCH` verb..

### What did you expect to happen?

Expected `CREATE` to be called with `CREATE` field validation without looking at the `PATCH` endpoint.

### How can we reproduce it (as minimally and precisely as possible)?

Create Open API v3 specification with a field validator.  Storage for API server (aggregated API server) advertises support only for `CREATE`, `GET`, `DELETE`

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.28.9
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.28.9-gke.1000000
```

</details>


### Cloud provider

<details>
GKE
</details>


### OS version

<details>

    architecture: amd64
    bootID: f993a6ef-ee9e-457b-856e-bfd51f9cdd22
    containerRuntimeVersion: containerd://1.7.13
    kernelVersion: 5.15.0-1054-gke
    kubeProxyVersion: v1.27.12-gke.1190000
    kubeletVersion: v1.27.12-gke.1190000
    machineID: 4da31cf9d84cf8d82e680abcb09130ae
    operatingSystem: linux
    osImage: Ubuntu 22.04.4 LTS
    systemUUID: 4da31cf9-d84c-f8d8-2e68-0abcb09130ae

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>

--- end body ---
