Is your feature request related to a problem? Please describe.

We follow certain steps every few months when a new release of k8s comes out. Below are the some of the steps that generally need to be followed:

• First creating a PR to add a custom test job so that we can test if things work on the new version without merging the actual upgrade: Preparing k8s v1.34 test suite testing#1108
• Then fix(ci): upgrading to v1.34 for CI and local tests #8073 raising the actual PR to upgrade the version and see if the new custom job passes. If it does merge the PR
• Making 1.34 default for master testing#1109 change the default k8s version in prowgen/spec.go.

Describe the solution you'd like

Look into how renovate could help to automate some of these steps.

Describe alternatives you've considered

Additional context

Environment details (remove if not applicable):

• Kubernetes version:
• Cloud-provider/provisioner:
• cert-manager version:
• Install method: e.g., helm/static manifests

/kind feature