Implement GUI Automation Test Commands and Refactor AsarWrapper Usage

- Added new test commands for GUI automation in `test_commands.cc`, including handling test runs, statuses, listings, and results.
- Refactored instances of `app::core::AsarWrapper` to `core::AsarWrapper` across multiple files for consistency.
- Updated CMake configuration to include new test command files.
- Modified integration and unit tests to reflect the changes in AsarWrapper usage.
- Ensured proper error handling and output formatting for test commands.

docs/z3ed/REMOTE_CONTROL_WORKFLOWS.md

@@ -201,7 +201,7 @@ z3ed agent discover --pattern "*/button:*"
 
 ### Test Harness Changes
 
-**File**: `src/app/core/imgui_test_harness_service.cc`
+**File**: `src/app/core/service/imgui_test_harness_service.cc`
 
 **Changes**:
 1. Added widget registry include
@@ -390,7 +390,7 @@ steps:
 - [E2E_VALIDATION_GUIDE.md](E2E_VALIDATION_GUIDE.md)
 
 **Code Files**:
-- `src/app/core/imgui_test_harness_service.cc` - Test harness implementation
+- `src/app/core/service/imgui_test_harness_service.cc` - Test harness implementation
 - `src/app/gui/widget_id_registry.{h,cc}` - Widget registry
 - `src/app/editor/overworld/overworld_editor.cc` - Widget registrations
 - `scripts/test_remote_control.sh` - Test script