[ACM Obs bot] Bump stolostron/kube-state-metrics to v2.13.0

[acm-observability-bot]

Description

This is an automated version bump from CI.
The logs for this run can be found in the syncbot repo actions.
If you wish to perform this manually, execute the following commands from stolostron/kube-state-metrics repo:

git fetch https://github.com/kubernetes/kube-state-metrics --tags
if ! git merge refs/tags/v2.13.0 --no-edit; then
  git checkout --theirs CHANGELOG.md  docs go.mod Dockerfile
  git checkout --ours VERSION OWNERS
  git add CHANGELOG.md  docs go.mod Dockerfile VERSION OWNERS
  git merge --continue
fi
go mod tidy
go mod vendor

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: acm-observability-bot[bot]
Once this PR has been reviewed and has the lgtm label, please assign douglascamata for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

Hi @acm-observability-bot[bot]. Thanks for your PR.

I'm waiting for a stolostron member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[openshift-ci]

The following users are mentioned in OWNERS file(s) but are untrusted for the following reasons. One way to make the user trusted is to add them as members of the stolostron org. You can then trigger verification by writing /verify-owners in a comment.

• CatherineF-dev
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
• dgrisonnet
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
  • OWNERS
• logicalhan
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
• mrueg
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
  • OWNERS
• rexagod
  • User is not a member of the org. User is not a collaborator. Satisfy at least one of these conditions to make the user trusted.
  • OWNERS

[openshift-merge-robot]

PR needs rebase.

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.