Upgrade Dash board

[yiraeChristineKim]

Summary

Upgrade the dashboard to a more stable and maintainable baseline (frontend + API integration), and fix reliability issues in cluster detail views (especially Add-ons) caused by inconsistent response payloads.

Background

The dashboard currently has mixed API response assumptions and a few quality gaps that make upgrades risky and can lead to runtime blank screens in some tabs.

Goals

• Upgrade dashboard dependencies and align build/lint configuration.
• Improve resiliency of API response handling in cluster detail pages.
• Eliminate blank-page failures in Add-ons and related tabs.
• Keep existing behavior for cluster list/detail workflows.

Scope

• Frontend (dashboard/src) dependency and compatibility upgrades.
• API client hardening for response shape handling (array vs object-with-items, nullable nested fields).
• Validation of cluster detail tab rendering (Overview, Add-ons, ManifestWorks).
• Build/lint cleanup required for upgrade completion.

[yiraeChristineKim]

@rokej

[mikeshng]

Let's work together with @annelaucg and her team on the OCM UI.

@augustrh mentioned he would like to hedge towards https://headlamp.dev/ as well.

We should discuss in https://kubernetes.slack.com/channels/open-cluster-mgmt on steps forward regarding OCM UI.

[augustrh]

The headlamp team was looking for projects to get involved with. I think this would work well for OCM.

[annelaucg]

We have made some expanded functionality specifically for ManifestWorkReplicaSet and Placements for our own use case. Definitely want to align with OCM community plan for UI.

CC: @grimlock-sfdc

[augustrh]

We have made some expanded functionality specifically for ManifestWorkReplicaSet and Placements for our own use case. Definitely want to align with OCM community plan for UI.

Awesome! We're at a point where we wanna pick a direction and go with it. @annelaucg are you in the OCM K8s slack? I'm super keen to get community input here: https://kubernetes.slack.com/archives/C01GE7YSUUF