Fix for false ERROR status during long vPro activation

[ipsita-npg]

Description

Problem statement:
During vPro activation, the synchronous/blocking AMT activate command blocks for 30-60+ seconds, preventing lastCheckTimestamp updates during activation process. This causes the health check to report STATUS_NOT_READY, incorrectly transitioning the host to ERROR state in the UI

Fixes # (issue)

• Implement async activation with statusUpdateCallback mechanism
• Update lastCheckTimestamp during long activation process
• Report proper activation status (ACTIVATING/ACTIVATED/FAILED) to dm-manager (Here This is not a health status update to node agent . The activation was converted to an asynchronous so wanted to check all the report status to DM manager / Inventory/ UI)

Validation :
Thorough validation is required since the existing logic and design have been modified.
This scenario can be properly validated after a failure: Activation status transitions to ACTIVATION_FAILED and the UI shows “Failed” or "Error" instead of progress

Complete failed activation: ( This scenario is mentioned because activation is currently implemented as an async call, just to verify whether all activation failure messages are correctly shown in the UI status field.)
UI status transitions from “In Progress” to “Failed”, Agent count remains 10/10 and Host shows an activation error (not an agent error) ----> This scenario needs to be validated

Any Newly Introduced Dependencies

Please describe any newly introduced 3rd party dependencies in this change. List their name, license information and how they are used in the project.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• I agree to use the APACHE-2.0 license for my code changes
• I have not introduced any 3rd party dependency changes
• I have performed a self-review of my code