Fixed RKE cluster being shown as Imported

[eva-vashkevich]

Summary

Fixes #6836

We were not identifying RKE1 clusters correctly.

Occurred changes and/or fixed issues

Changed the way we identify cluster provisioner type to recognize RKE1 clusters correctly and moved the logic to determine if cluster is imported from the Cluster Provider component to the model for better consistency.

Technical notes summary

Areas or cases that should be tested

Cluster management and Home pages should be showing correct "provider" field for each cluster.
Cluster edit should be showing correct fields.

Tested using Chrome 117.0.5938.132
Tested localy:
RKE1 is showing correct info as local and as imported clusters.
K3s is showing correct info as local, created through UI and imported clusters.
RKE2 is showing correct info as local and imported clusters.
AKS is showing correct info as created and imported cluster.

Areas which could experience regressions

Cluster edit might be affected.

Screenshot/Video

[momesgin]

@eva-vashkevich Just curious what happens to imported k3s clusters, as of my understanding provisioner() would return ‘k3s’, then isImported() would return false, and consequently isImportedK3s() would also return false, is this intentional?

I actually just read the old comment about the workaround, so based on that isImported() would probably return true

[eva-vashkevich]

@momesgin I've checked and it does identify imported k3 correctly, though your comment made me re-check rke2 case and I was missing identifying DO correctly, so thank you.

[momesgin]

@momesgin I've checked and it does identify imported k3 correctly, though your comment made me re-check rke2 case and I was missing identifying DO correctly, so thank you.

happy that it helped somehow 😆