Streaming cache output and stricter remote result validation

Live execution output is streamed through bounded pipes straight into the CAS instead of being buffered in full, reducing memory pressure on long-running actions. Tuist remote results whose referenced blobs cannot be materialized are now treated as cache misses rather than silent failures, and Daytona responses without an exit code are no longer accepted as successful action results.