RDKEMW-14517: Use IARM for PowerManager clients

[yuvaramachandran-gurusamy]

RDKEMW-14517: Use IARM based PowerManager

Signed-off-by: Yuvaramachandran Gurusamy [yuvaramachandran_gurusamy@comcast.com]

[Copilot]

Pull request overview

This pull request migrates the FrontPanel plugin from using the WPEFramework PowerManager COM-RPC interface to using IARM-based PowerManager for power state management. This change simplifies the architecture by removing the dependency on the PowerManager plugin interface and using direct IARM bus communication instead.

Changes:

• Replaced PowerManager COM-RPC interface with IARM bus calls for power state queries and event notifications
• Removed PowerManagerInterfaceRef and associated notification handler infrastructure
• Simplified CFrontPanel::instance() to no longer require PluginHost::IShell parameter

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
helpers/frontpanel.h	Removed PluginHost::IShell parameter from instance() method signature
helpers/frontpanel.cpp	Replaced PowerManager interface with direct IARM_Bus_Call for power state queries
FrontPanel/FrontPanel.h	Removed PowerManagerNotification class and related members; added IARM initialization methods
FrontPanel/FrontPanel.cpp	Replaced PowerManager event registration with IARM event handler registration; implemented IARM-based power mode change handling

[Copilot]

The logging format string contains '\r' (carriage return) which is inconsistent with other LOGINFO statements in the codebase. Line 275 uses '\n' (newline) instead. For consistency, this should use '\n' or no line ending at all, as LOGINFO likely adds its own line termination.

Suggested change

	LOGINFO("Event IARM_BUS_PWRMGR_EVENT_MODECHANGED: State Changed %d -- > %d\r",
	LOGINFO("Event IARM_BUS_PWRMGR_EVENT_MODECHANGED: State Changed %d -- > %d",

[Copilot]

The variable 'res' is declared but never used after the IARM_CHECK macro call. The IARM_CHECK macro internally uses 'res', but this requires 'res' to be declared in the scope. However, this pattern creates unused variable warnings in some contexts. Consider whether the variable is needed or if the macro handles all necessary error checking internally.

[Copilot]

The variable 'res' is declared but never used after the IARM_CHECK macro call. This is the same pattern as in InitializeIARM. Consider whether the variable is needed or if the macro handles all necessary error checking internally.

[Copilot]

The IARM_Bus_Call result is checked, but if it fails (res != IARM_RESULT_SUCCESS), powerStatus remains false without any logging or error handling. This differs from the previous implementation which logged the power state. Consider adding error logging when the IARM call fails to aid debugging.

Suggested change

	powerStatus = true;
	powerStatus = true;
	} else {
	LOGERR("IARM_Bus_Call(%s, %s) failed with result %d; leaving powerStatus as %d",
	IARM_BUS_PWRMGR_NAME, IARM_BUS_PWRMGR_API_GetPowerState, res, powerStatus);