Wire in new status.condition property

[richard-cox]

• blocker on steve bump to rancher/rancher (to get fix for BE filter bug)

Summary

Fixes #13268

Occurred changes and/or fixed issues

• as per title, now that the v1 mgmt cluster status.connected property is supported wire it in

Areas or cases that should be tested

• side nav cluster list should order clusters in
  • local cluster
  • running
  • name

Areas which could experience regressions

• side nav

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

[richard-cox]

Linking rancher/rancher#48993

[codyrancher]

The title of this pr seems to think we're supposed to be using status.condition

[codyrancher]

The description of this pr also mentions something like:

1. local cluster
2. working clusters
3. name

But judging from the issue I think 3. name is supposed to read 3. everything else

[codyrancher]

I don't actually see a difference between what I see in master vs what I see in this branch. Both seem to have the same order. But I don't see any harm in what's going on either so feel free to merge.