Better Error Reporting

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

I deployed k0s with NO cni enabled, as I installed cilium after the fact. The bootstrap reports "workers failed to be come ready". It should have been obvious to me that this should have been an expected response, when no cni has been bootstrapped.

If the config file has the cni disabled, then the boot strap should change how it determines a successful boot strap. Or at least post a warning as to by the ready state failed.

I had another bootstrap failure when there was two interfaces on the worker nodes, one for k8s and one for storage. Because I didn't spec a interface name, the bootstrap chose the wrong interface. Again no reporting that this was the case.

In short, I would like to have better failure reporting. However this distribution is one of the best I have used, and I am greatfull for all the hard work.

### Describe the solution you would like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Start by reproducing bootstrap with CNI disabled and with worker nodes having separate Kubernetes and storage interfaces. Trace the bootstrap readiness check and interface selection entry points, then define done as reporting the expected CNI state and clearly identifying when the wrong or unspecified interface prevents readiness.

Written by the indexing model from the issue text.