Release release-0.7

[CatherineF-dev]

What happened: release-0.6 is still using k8s.io/apiserver v0.23.17, which has some vulnerabilities.

What you expected to happen:

Anything else we need to know?:

Environment:

• Kubernetes distribution (GKE, EKS, Kubeadm, the hard way, etc.):

• Container Network Setup (flannel, calico, etc.):

• Kubernetes version (use kubectl version):

• Metrics Server manifest

spoiler for Metrics Server manifest:

• Kubelet config:

spoiler for Kubelet config:

• Metrics server logs:

spoiler for Metrics Server logs:

• Status of Metrics API:

spolier for Status of Metrics API:

```sh kubectl describe apiservice v1beta1.metrics.k8s.io ```

/kind bug

[k8s-ci-robot]

This issue is currently awaiting triage.

If metrics-server 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](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[CatherineF-dev]

cc @dgrisonnet could we release v0.7?

[dgrisonnet]

I don't have the bandwidth to shepherd the release, but if you want, we can do it together.

All the steps to release metrics-server are documented in https://github.com/kubernetes-sigs/metrics-server/blob/master/RELEASE.md, so if you have the time to go through it, I can help you with reviews and anything that need write permissions.

I will close this issue in favor of #1165 to avoid duplication.