Fix: Handling GTEST_FAIL logic for multi-device scenario for Engine, Fabric and Overclocking modules

[viki435]

Primary JIRA: VLCLJ-2513
Sub-tasks: VLCLJ-2573, VLCLJ-2569, VLCLJ-2571
Fix: Handling GTEST_FAIL logic for multi-device scenario for engine, fabric and overclocking modules.

[Copilot]

Pull Request Overview

This PR fixes handling of GTEST_FAIL logic for multi-device scenarios in the Engine, Fabric, and Overclocking test modules. The changes address an issue where tests would fail immediately if any single device didn't support the required features, even when other devices in the system might support them.

• Replaced immediate FAIL() calls with device-specific checks and logging
• Added class member variables to track feature support across all devices
• Moved final FAIL() logic outside device loops to only fail if no devices support the feature

Reviewed Changes

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

File	Description
test_sysman_overclocking.cpp	Added is_frequency_supported flag and restructured tests to check all devices before failing
test_sysman_fabric.cpp	Added is_fabric_supported flag and restructured tests to check all devices before failing
test_sysman_engine.cpp	Added is_engine_supported flag and restructured tests to check all devices before failing

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[vishnu-khanth]

LGTM!