Add execution strategy pattern to support Docker, Wine, WSL, and Windows Sandbox

[Copilot]

Executors currently execute directly on the host OS. This adds support for running implementations in containerized/virtualized environments (Docker, Wine, WSL, Windows Sandbox) with proper path mapping and binding translation.

Changes

• New interfaces

  • IExecutionStrategy: Strategy for executing in specific environments
  • IExecutionContext: Abstracts process execution context
  • IPathMapper: Translates paths between host and target environments

• Strategy implementations

  • NativeProcessStrategy: Existing behavior (default)
  • DockerStrategy: Mounts implementations as volumes, maps to /0install/* paths
  • WineStrategy: Maps Linux paths to Wine Z:\ drive, handles WINEPREFIX
  • WSLStrategy: Converts Windows paths to /mnt/*, invokes via wsl.exe
  • WindowsSandboxStrategy: Generates .wsb config, uses SHA256 for deterministic path mapping

• Integration

  • Executor accepts optional IExecutionStrategy parameter
  • Each strategy handles EnvironmentBinding, ExecutableInVar, ExecutableInPath with appropriate path translation

Usage

// Backward compatible - defaults to native execution
var executor = new Executor(implementationStore);

// Execute in Docker container
var executor = new Executor(implementationStore, 
    new DockerStrategy("ubuntu:latest"));

// Execute via WSL
var executor = new Executor(implementationStore, 
    new WSLStrategy("Ubuntu"));

executor.Start(selections);

All bindings are translated to target environment paths automatically. Custom strategies can be implemented via IExecutionStrategy.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Generalize ZeroInstall.Services.Executors to support Docker, Wine, WSL and Windows Sandbox</issue_title>
<issue_description>Currently, the services in ZeroInstall.Services.Executors only support launching applications directly on the OS 0install is running on.

We should generalize this, so that it can also orchestrate executing applications inside environments like:

• Docker containers (running Linux binaries on Windows and Linux)
• Wine (running Windows binaries on Linux)
• WSL (running Linux binaries on Windows)
• Windows Sandbox (running Windows binaries on Windows)

For each of these cases it will be necessary to:

• map cached implementation directories into the target system
• handle bindings
  • for EnvironmentBindings, paths need to be translated and env vars need to be applied inside the target system
  • for ExecutableInVars and ExecutableInPaths, stub executables need to be generated for the target OS and mapped in</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Generalize ZeroInstall.Services.Executors to support Docker, Wine, WSL and Windows Sandbox #277

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.