☂️: implementation for the Scenario feature

[sanposhiho]

A looong time ago, we created a KEP for the feature called Scenario.
https://github.com/kubernetes-sigs/kube-scheduler-simulator/tree/master/keps/140-scenario-based-simulation

Let's start the basic implementation based on the proposal.
I know there could be multiple tasks: this issue would be an umbrella issue and feel free to create individual issues.

### Tasks
- [ ] xxx

[sanposhiho]

/cc @utam0k @ordovicia @saza-ku @YamasouA

who I heard the interest in this feature.

[sanposhiho]

Just FYI, I actually have a draft branch that me two years ago worked on, which I don't remember at all anymore.. 😅
https://github.com/sanposhiho/kube-scheduler-simulator/tree/implement-sceario-controller-phase1
Feel free to refer to or completely ignore it when implementing...

[saku3]

I am interested in this issue and would like to take on the challenge.
First, I plan to update Golang, Kubebuilder, and other dependencies related to the Scenario object to the latest versions.

[sanposhiho]

There are some people I heard interests contributing to this feature, and we should try avoiding the double efforts made by different people. Folks, please mention what you're going to start before actually starting so that we can prevent such unlucky situation.

[YamasouA]

I want to implement ScenarioOperation.
Can I try it?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten