fix k0s reset bug.

[starComingup]

Signed-off-by: starComingup 1225067236@qq.com

Describe what this PR does / why we need it

k0s nodes reset do not need to specify --config so this made sealer delete failed. In this PR, resolve this bug.
And master nodes will set default config path:/etc/k0s/k0s.yaml/ which same as our config path,

Does this pull request fix one issue?

NONE

[allencloud]

Actually there are no test case for k0s now. So I am afraid that almost no one of maintainers has the ability to review your code. So I wish that we could add k0s test case or improve the test framework to guarantee the code update could satisfy the test case. How about that?

Although we have no test, for the pull request of this one, I could make it move on and merging. @starComingup

[starComingup]

Actually there are no test case for k0s now. So I am afraid that almost no one of maintainers has the ability to review your code. So I wish that we could add k0s test case or improve the test framework to guarantee the code update could satisfy the test case. How about that?

Although we have no test, for the pull request of this one, I could make it move on and merging. @starComingup

@allencloud I have been tested it and fix problems one by one. As for auto build basefs, it need some time to do that. If somebody want to help me to test, I would appreciate it！
there is a public image can be used to test registry.cn-hangzhou.aliyuncs.com/starcoming/k0s:v1.24.4