`Job.spec.podReplacementPolicy´ being classified as `Alpha` feature even though it is graduated

When checking the [reference documentation](https://v1-34.docs.kubernetes.io/docs/reference/kubernetes-api/workload-resources/job-v1/) of the `batch/v1` `Jobs` API in version `[v1.34](https://v1-34.docs.kubernetes.io/docs/reference/kubernetes-api/workload-resources/job-v1/)` or `[v1.35](https://kubernetes.io/docs/reference/kubernetes-api/workload-resources/job-v1/)` you can find `podReplacementPolicy` in the `Alpha level` section of the [`JobSpec`](https://v1-34.docs.kubernetes.io/docs/reference/kubernetes-api/workload-resources/job-v1/#JobSpec).

This is surprising as the feature apparently graduated in `v1.34` (see [release blog](https://kubernetes.io/blog/2025/08/27/kubernetes-v1-34-release/#delayed-creation-of-job-s-replacement-pods), [KEP-3939](https://kep.k8s.io/3939)).

I would prefer this to be corrected in place, i.e. for `v1.34` and `v1.35`, but if this is not feasible, please fix it for the minor release (`v1.36`).

`podReplacementPolicy` seems to fit nicely into the `Lifecycle` section of `JobSpec` from my point of view.