Power State API doesn't timeout if device is not actually connected to MPS

[msbreton]

Describe the bug 🪲
If you call /api/v1/amt/power/state/{guid} when a device is CIRA disconnected, but MPS has not yet updated the state (has not yet timed out and connectionStatus is still true) then MPS doesn't timeout and does not return a proper status code.

To Reproduce 🪜
Steps to reproduce the behavior:

1. Activate device in CCM / CIRA
2. Connect device
3. Remove network cable
4. In less than 90 seconds, call /api/v1/amt/power/state/{guid}

Expected behavior
API should timeout in a reasonable time (15 seconds?) and respond with a proper status code (404?).

Screenshots 🖼️
If applicable, add screenshots to help explain your problem.

AMT Device (please complete the following information): 🖥️

• OS: [e.g. Linux Kernel & Version]
• AMT Version: [e.g. 11.8.5, 12.0.45]
• AMT Configuration Mode: [e.g. Admin Control Mode or Client Control Mode]
• Network Configuration [e.g. Dynamic IP or Static IP]

Service Deployment (please complete the following information): ⛈️

• Deployment Type: [e.g. Azure, Docker, K8s]
• Node Version: [e.g. LTS 14]
• Component & Version: MPS version 2.13.10.

Additional context
Here is the code we suspect is missing the timeout.
https://github.com/open-amt-cloud-toolkit/mps/blob/bb713a3e62f4d0abcbb98923892ba1ad7a699c6a/src/routes/amt/getPowerState.ts#L15

[mjdivankoller]

I have followed the reproduction steps successfully, and the situation is effectively exposed.

1. I have activated the device in CCM/CIRA mode

2. I request the current power state with a response below 2 seconds (End-to-End)

Please take a look at the log messages for a successful request here.

3. I request the current power state, but I unplug the cord in the middle.
   Initially, it waits for the response, showing the device as "connected."
   
   After 2 mins (in this case), Postman remains waiting for the response; however, the web interface has updated the status as disconnected.
   
   Postman remains waiting for a response even after 10+ minutes.

Please take a look at the log messages for this scenario.
Successful Scenario:
20250424-getPowerState_OK.txt
Unplugging the cord immediately after the request and plugging it again after a while:
20250424-getPowerState_Unplug_andPlug.txt

Verified it!

[mjdivankoller]

A solution has been found and implemented.
It implements a race between a timer for timeout and the Promise related to the functionality. It is generally implemented to be used as a reference in other API calls. The getPowerState API call incorporates its use and test cases.

It is available for review in PR#1929

Example of the 404 response with the timeout (The getPowerState API call):