setup scheduler with the wasm extension

[sanposhiho]

What would you like to be added:

### Tasks
- [x] create the scheduler with the wasm extension
- [x] create `registry.k8s.io/kube-scheduler-wasm-extension/scheduler` to provide the scheduler in which the wasm extension is enabled

Why is this needed:

We will eventually try to include this wasm extension into the upstream, but it's worth having the scheduler binary/image here meanwhile regardless.

I'll work on this since I recently worked on the registry stuff in the simulator and understand the process.

/assign /cc @kerthcet

[kerthcet]

create the scheduler with the wasm extension

Do you mean you want to build a new scheduler supporting wasm extension? but where to hold this project? On your own k/k project?

[sanposhiho]

I meant building the scheduler with our wasm extension plugin Just like scheduler-plugins does: https://github.com/kubernetes-sigs/scheduler-plugins/blob/master/cmd/scheduler/main.go

[kerthcet]

Got it, plz go ahead.

[k8s-ci-robot]

@sanposhiho: The label(s) `priority/next-releas``` cannot be applied, because the repository doesn't have them.

In response to [this](https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension/issues/9#issuecomment-1872438015): >/priority next-releas`` 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.

[sanposhiho]

/priority next-release

[sanposhiho]

Still there is a remaining step for the registry.