Add support for unpackaged Windows apps in TCP tests

[Copilot]

This PR adds support for unpackaged Windows applications (.exe files) in the TCP test workflow by introducing a new windows test-unpackaged command.

Changes Made

New Command: windows test-unpackaged

• Purpose: Run TCP tests with unpackaged Windows applications (.exe files)
• Key differences from packaged apps:
  • No certificate management required
  • No MSIX installation/uninstallation
  • Direct process launch via Process.Start()
  • Simple process termination for cleanup

Implementation Details

• Added WindowsUnpackagedTestCommand class extending BaseTestCommand
• Reuses existing TCP listener functionality from the base class
• Validates input files are .exe extensions
• Includes proper error handling and cleanup
• Added comprehensive unit tests

Usage Examples

# Basic usage
devicerunners windows test-unpackaged --app path/to/app.exe

# With custom port
devicerunners windows test-unpackaged --app path/to/app.exe --port 8080

# With custom timeouts
devicerunners windows test-unpackaged --app path/to/app.exe --connection-timeout 60 --data-timeout 45

Testing

• All existing tests continue to pass (34/34)
• Added comprehensive test coverage for the new command
• Validated error handling for missing files and non-exe files
• Tested JSON output format compatibility

This implementation follows the existing architecture patterns and maintains backward compatibility while providing the requested functionality for unpackaged Windows applications.

Fixes #67.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[mattleibow]

Thins must not be a separate command, just check the extension of the app in the test command and do the different thing.

Also, demonstrate this in a new pipeline

[Copilot]

Thins must not be a separate command, just check the extension of the app in the test command and do the different thing.

Also, demonstrate this in a new pipeline

Done! I've refactored the implementation as requested:

1. Removed separate command: Deleted WindowsUnpackagedTestCommand and combined functionality into the existing windows test command
2. Extension-based detection: The command now checks Path.GetExtension() and routes to different logic:
   • .exe files → unpackaged app flow (direct process launch, no certificates)
   • .msix files → packaged app flow (existing MSIX logic)
3. New pipeline: Added test-tcp-windows-unpackaged.yml that publishes as a self-contained .exe and tests it

Key changes in commit 865f599:

• Modified WindowsTestCommand with ExecuteUnpackagedApp() and ExecutePackagedApp() methods
• Updated command description to indicate support for both file types
• Added comprehensive tests for both paths
• All existing tests pass (32/32)

The command now works seamlessly with both file types using the same windows test command.