[docker/cli] Support accessing sandbox-internal services from the host machine

### ROOT CAUSE The issue arises because the sandbox container operates in an isolated network namespace by default, preventing host access to its internal services. The solution involves modifying the network configuration to integrate the sandbox container with the host's default bridge network, allowing seamless access via container names or IP addresses. ### CODE FIX ```go // In pkg/sandbox/sandbox.go, modify the network creation to use the host's default bridge // Replace the existing network creation with: networkMode := "bridge" // Use the default bridge network by removing any custom network creation // Then, update the container run command to use this network mode // Example change in the Run() method: // Before: // cmd = exec.Command("docker", "run", "--network", "custom-sandbox-network", ...) // After: // cmd = exec.Command("docker", "run", "--network", "bridge", ...) ``` This change ensures the sandbox container shares the host's default bridge network, enabling host access to sandbox services via their names or IPs.