k0s autopilot plan management

[dvirassamy]

Is your feature request related to a problem? Please describe.

I have to use only one name for an autopilot plan. And I can only have one plan with that same name in the Plan custom resource.

1. Issue 1 - I do not keep a history of my plans (like jobs)
2. I need to remove a plan before being to fix a broken plan or applying a new upgrade

I also need to manage the ids to avoid ControlNode annotation conflicts (the latter keeps track of previous operations). For example adding a new plan with the same id as a previously successful plan would cause the newly added plan status to directly become successful without actually applying the change.

Describe the solution you would like

1. Define a flexible plan name (standard kube naming convention)
2. Keep history of the plans (like jobs) (for failed and successful)
3. Improve ControlNode annotations
4. Get better monitoring of running plans, events and status of plans

Describe alternatives you've considered

No response

Additional context

Users are confused on how to use plans, where to look when you have issues and how to fix the different objects.