Clicking the Refresh Power Status icon does not retrieve the latest power state

[graikhel-intel]

Description

The Refresh Power Status icon on the Device Details page should retrieve the latest power state from the device and update the power status displayed in the UI.

Currently, clicking the icon does not trigger a request to retrieve the latest power state, leaving the displayed status stale. This appears to be a regression.

The periodic power state refresh timer is already being tracked separately under issue #3333 and is out of scope for this issue.

Steps to Reproduce

1. Navigate to the Device Details page.
2. Open the browser developer tools and monitor the Network tab.
3. Click the Refresh Power Status icon.
4. Observe that no request is made to retrieve the latest power state and the displayed power status does not change.

Expected Behavior

• Clicking the Refresh Power Status icon should immediately retrieve the latest power state from the device.
• The power status icon should update based on the latest response.
• The UI should reflect the current device power state after the request completes.

Screenshot

Acceptance Criteria

• Clicking the Refresh Power Status icon retrieves the latest power state from the device.
• The power status displayed in the UI is updated based on the latest response.
• Existing periodic power state refresh remains tracked under issue #3333.
• Standard DoD

[DevipriyaS17]

With CIRA connected, the device stays reachable through the live APF/Wsman tunnel, so the refresh can hit the backend and you see the /api/v1/amt/power/state/:guid request. Without CIRA, clicking refresh does not produce that backend call, so the UI keeps showing stale power state.

This does not need a console backend fix because the console backend already has the power-state endpoint and handler in power.go. The bug is in the frontend refresh behavior: the button is using the cached power-state path instead of forcing a fresh read, so the request never reaches the backend in the non-CIRA case. In other words, the backend is responding correctly when called; the missing piece is the UI click path that decides whether to fetch fresh state or reuse cached state.

This issue should be tracked in the sample-web-ui repo. @graikhel-intel, @sudhir-intc, could one of you please move it there?

[sudhir-intc]

@DevipriyaS17 : Thanks for the analysis. moved the issue to the sample-web-ui repo. Also please check the behavior with mps/rps too.