Warm test builds stay incremental when dependency module maps are generated

Tuist no longer rewrites generated dependency module maps when their contents have not changed, and keeps Derived/ModuleMaps and Derived/FrameworkSearchPaths across generation. This prevents Xcode from treating stable compiler inputs as changed, so tuist test –build-only stays warm and avoids unnecessary Swift recompilation.