chore: Prep release v2.13.0

[mrueg]

What this PR does / why we need it:
Preparing for next release.
How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)
None
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2406

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[CatherineF-dev]

Use 2.13.0 instead #2375

[grigoni]

Hi folks
To my understanding there will be no 2.12.x release
This opens two questions:
Will this release also support k8s 1.29.x?
How this project manages CVEs for current supported K8s versions?

thanks
Gianandrea

[rexagod]

Can we include #2418 as well?

[jeremyrickard]

Hey folks, do you need any help with these releases? Is there something community members can help with?

[mrueg]

Thanks for the offer! There are two more issues, we would want to resolve before the next release: https://github.com/kubernetes/kube-state-metrics/milestone/6

In general, yes. If someone in the community would want to help increasing the release cadence that would be super helpful! Let's chat in #kube-state-metrics in k8s slack.

[rexagod]

/lgtm
/hold

(for others, feel free to unhold)

Thank you for running this! 🙂

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mrueg, rexagod

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mrueg,rexagod]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mrueg]

/hold cancel

To move ahead with the release.