Fixed imported cluster not being recognized correctly in 'Waiting' state

[eva-vashkevich]

Summary

Fixes #13472

Waiting status is a special case, which was not considered by our existing logic, so we were not correclt identifying such cluster as imported.

Occurred changes and/or fixed issues

Added a new special condition to cover missed case.

Technical notes summary

Areas or cases that should be tested

1. Import a k3s or rke2 cluster
2. When the State changes to "Waiting", attempt to Edit Config
3. Imported cluster edit should open, no ember should be loaded

Areas which could experience regressions

Imported hosted providers and provisioned rke2/k3s clusters could be affected.

Screenshot/Video

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility
• The PR has considered, and if applicable tested with, the three Global Roles Admin, Standard User and User Base

[richard-cox]

is this fine for types like custom?

[eva-vashkevich]

@richard-cox I've tried provisioning a custom cluster and didn't notice any regressions

[mantis-toboggan-md]

LGTM I verified that the correct edit page is loaded, and the table 'Provider/distro' column has no regressions, in both 'waiting' and 'active' state, for the following

• generic imported (k3s)
• imported AKS
• provisioned k3s
• provisioned AKS

[richard-cox]

Clearing stale review, and going on #16213 (review) approving