[proposal] add cri v1 api to koord-runtime-proxy

[maaoBit]

What is your proposal:
Koord-runtime-proxy support cri v1 api, and support v1alpha in parallel

Why is this needed:
According to kubernetes/kubernetes#110618, k8s v1.26 removed cri v1alpha2 support.
In order to run on k8s 1.26+, koord-runtime-proxy support cri v1 api.

Is there a suggested solution, if so, please add it:

[stale]

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close
  Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Reopen this PR with /reopen
  Thank you for your contributions.

[hormes]

/reopen

[koordinator-bot]

@hormes: Reopened this issue.

In response to this:

/reopen

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/test-infra repository.

[hormes]

Let me sort out the ideas, the support of cri-api api version:

version	cri-api supported	kubelet import
1.19	v1alpha2	v1alpha2
1.20	v1alpha2, v1	v1alpha2
1.21	v1alpha2, v1	v1alpha2
1.22	v1alpha2, v1	v1alpha2
1.23	v1alpha2, v1	v1
1.24	v1alpha2, v1	v1
1.25	v1alpha2, v1	v1
1.26	v1	v1

We try our best to be compatible with various usages, and transparently forward unsupported interfaces to the backend.

[stale]

This issue has been automatically marked as stale because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close
  Thank you for your contributions.

[stale]

This issue has been automatically closed because it has not had recent activity.
This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, the issue is closed
  You can:
• Reopen this PR with /reopen
  Thank you for your contributions.