Feature request: Add support for Modern Standby - Standby (S0 Low Power Idle) Network Connected to power/action API

[msbreton]

Describe the bug 🪲

Feature request
Newer platforms running Windows 10 and Windows 11 commonly come from OEMs configured to use Modern/Connected Standby vs, traditional standby.

Currently /api/v1/amt/power/action/{guid} "action": 2, will not wake a system in Modern/Connected Standby. It will return 200 but the system will remain in Modern/Connected Standby. To wake a system in that state, you need to call PowerManagementService.RequestOSPowerSavingStateChange with "Full Power" as "OSPowerSavingState",

One possible way to support both normal wake from normal standby and Modern standby is to 1st check the current power state and then send the appropriate power on commend. For example:

If the power state is "OS power saving", call IPS_PowerManagementService.RequestOSPowerSavingStateChange with "Full Power" as "OSPowerSavingState",
if the OS power state is different of "OS power saving" continue doing the power action as usual.

AMT SDK reference here.

To Reproduce 🪜
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

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: [e.g. RPS 2.0.0]

Additional context
Add any other context about the problem here.