Warm test builds stay incremental when generated dependency module maps are unchanged

Tuist now preserves file modification times for generated files whose contents have not changed, and keeps active Derived/ModuleMaps and Derived/FrameworkSearchPaths directories stable across generation. This fixes a regression where warm tuist test –build-only runs recompiled Swift files unnecessarily because generated module map inputs looked newer even though their contents were identical.