Warm test –build-only stays incremental when generated module maps are unchanged

Generated dependency module maps and framework search path response files are no longer rewritten when their contents have not changed. Tuist also preserves Derived/ModuleMaps and Derived/FrameworkSearchPaths during early project cleanup while still removing stale generated files. This keeps tuist test --build-only incremental across warm generation invocations when the generated compiler inputs are unchanged.