fix: add custom deserializer for PSU's power state attribute to handle both string and boolean values.

[spydaNVIDIA]

GB200s report the PSU power state as a string: "On"/"Off"
Liteon PMCs report the PSU power state as a boolean: true/false

Querying a powershelf before the changes:

spyda@control72-cno1-cp1-jhb01:~$ ./carbide-admin-cli redfish --address 7.243.170.140 --username root --password 'password' --vendor lite-on-power-shelf get-power-state

Off

Querying a powershelf after the changes:

spyda@control72-cno1-cp1-jhb01:~$ ./carbide-admin-cli redfish --address 7.243.170.140 --username root --password 'password' --vendor lite-on-power-shelf get-power-state

On

[yoks]

Why try to read not in spec property for PSU? PowerState is present in:

• Chassis
• System
• Circuit
• Outlet
• Switch

PowerSupply does not have PowerState. This sounds like something super specific and brittle (as it relly not on spec fields).

[spydaNVIDIA]

Why try to read not in spec property for PSU? PowerState is present in:

• Chassis
• System
• Circuit
• Outlet
• Switch

PowerSupply does not have PowerState. This sounds like something super specific and brittle (as it relly not on spec fields).

The PowerState being reported via Chassis and System information is not accurate for the Liteon Powershelves. I found that the only reliable source for the power state of the powershelf came from querying each of the PSU's power states as reported by its power supply.