[Bug]: Consistent Error Propagation

[dkovba]

Created from #167.

I have done the following

• I have searched the existing issues
• If possible, I've reproduced the issue using the 'main' branch of this project

Steps to reproduce

Not applicable.

Current behavior

Inconsistent error propagation.

Expected Behavior

Consistent Error Propagation

• Errors should be properly propagated through the XPC hierarchy
• Failure states should be clearly communicated to clients
• Timeouts should be implemented for all operations

Graceful Recovery

• The system should recover from communication failures
• Resources should be properly released even when operations fail
• Failed operations should leave the system in a consistent state

Environment

Not applicable.

Code of Conduct

• I agree to follow this project's Code of Conduct

[dkovba]

An example where this is reproducible:

1. Trigger an error in vminitd, for example, by adding throw ContainerizationError(.internalError, message: "Important error message") to TerminalIO.start().
2. Run a container using bin/container run -it --rm alpine:latest date.

Results:

Error: interrupted: "internalError: "failed to start container" (cause: "interrupted: "XPC connection error: Connection interrupted"")
Ensure container system service has been started with `container system start`."