fix the version order of 'discovery.k8s.io'

[Iceber]

What type of PR is this?

/kind bug

What this PR does / why we need it:

Fixed the version order of discovery.k8s.io resource, wrong order could cause wrong prioritized version when using pkg/apis/disovery/install.Install.

This will also result in v1beta1 still being used as the storage version for endpointslice

$ /etcdctl --endpoints="https://127.0.0.1:2379"  --cert=/etc/kubernetes/pki/apiserver-etcd-client.crt --key=/etc/kubernetes/pki/apiserver-etcd-client.key --cacert=/etc/kubernetes/pki/etcd/ca.crt get --prefix /registry/endpointslices/default/kubernetes
/registry/endpointslices/default/kubernetes
k8s
)
EndpointSlice.io/v1beta1
...

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[pacoxu]

/sig api-machinery

[cici37]

/cc @alexzielenski If you would have time to review this one? Thank you!
/triage accepted

[pacoxu]

/cc @aojea
/assign @liggitt

[liggitt]

/remove-kind bug
/kind enhancement

This isn't a bug, we just never updated the storage version, which normally happens one release after adding the new version

[k8s-ci-robot]

@liggitt: The label(s) kind/enhancement cannot be applied, because the repository doesn't have them.

In response to this:

/remove-kind bug
/kind enhancement

This isn't a bug, we just never updated the storage version, which normally happens one release after adding the new version

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.

[liggitt]

/kind cleanup

[liggitt]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 859ea94270d4a4e36efde560f2e29a2ec7f7473e

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Iceber, liggitt

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:

• api/OWNERS [liggitt]
• pkg/apis/OWNERS [liggitt]
• pkg/controlplane/storageversionhashdata/OWNERS [liggitt]
• test/integration/etcd/OWNERS [liggitt]

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