Reuse unchanged chunks when sharing Xcode build outputs

Small source edits can produce large compilation outputs. Tuist's Xcode cache now uses content-defined chunking with compatible cache servers to avoid transferring unchanged parts of those outputs.

Uploads send only chunks the server is missing. Downloads reuse verified chunks retained on your machine, fetch the missing pieces, and reconstruct the exact original output. The bounded local chunk cache survives cleaning DerivedData and restarting the cache service. Existing clients and unsupported servers continue to use ordinary whole-output transfers.

In local generated-fixture benchmarks, changing one C function reduced its object's transfer payload by 47.4%, and renaming one property in a large Swift module reduced its payload by 27.8%. These measure transferred bytes, not build-time improvements; savings depend on the output, the edit, and which chunks remain cached. Compiler invalidation is unchanged.

See the Xcode cache guide for how chunk reuse works and how to configure existing and Tuist-generated projects.