Allow users to easily see expiring harvester cloud credentials and to renew them

[github-actions]

Epic: #11256 SURE-8516

This is a forwardport issue for #11270, automatically created via GitHub Actions workflow initiated by @richard-cox

Original issue body:

Requires expiring label on cloud cred

• Global notification somewhere warning of expired / soon to expire harv cloud creds
• Clearly see in cloud cred table expired / soon to expire (see cluster dashboard certs list for pattern?)
  • Column for sorting, only if harv cloud cred present?
• Sub row in harv clusters list to warn that cluster has a cloud cred that's expiring
• Cloud Cred bulk action to renew (recreate kubeconfig, update cloud cred)

Edit: Blocked on rancher/rancher#47241

[gaktive]

Leaving this as the 2.10.0 version since this was the forward port. Making the other one the backport but I'll emphasize that this ticket should be worked on first.

[gaktive]

This needs to line up with Harvester 1.4.0 which is set to come out before 2.10.0.

[richard-cox]

Update Train

• Iteration 1 - Warn users when creating a harvester cloud credentials that it will expire #11269
• Iteration 2 - Allow users to easily see expiring harvester cloud credentials and to renew them #11332 (this issue)
• Iteration 3 - Support Non-expiring Harvester Cloud Credentials Support #11271

Note - each issue is linked to a backport

[richard-cox]

Release note suggestion

In the Cloud Credential list users can now easily see if a Harvester Credential is about to or has expired and opt to Renew it. The Cluster Management Clusters list will also notify when an associated Harvester Cloud Credential is about to or has expired.

[yonasberhe23]

I do not see automation in the attached PR. moving to To Test for manual validation

[yonasberhe23]

@irishgordo would you mind taking this as you validated it for 2.9.3?

[khushboo-rancher]

@yonasberhe23 What is the timeline to close this, Harvester team is occupied with 1.4.0 release till Nov 7?

[richard-cox]

@khushboo-rancher this is part of the harvester token expiration feature, it's 2.9 counterpart is #11270 which was handled by @irishgordo. It might be best tackling once #12351 has merged as well (currently in review)

[m-ildefons]

I've validated that rancher/rancher#47667 has been fixed in v2.10.0-alpha7
I think this issue can be considered done?

[richard-cox]

thanks @m-ildefons , i'd be happy to close, @yonasberhe23 are you good too?

[izaac]

@richard-cox I've checked the test executed on rancher/rancher#47667 (comment) And it looks the coverage is good to validate the expectation of this issue. Moving to done.