Restore incremental warm generation for projects with generated module maps

Tuist now keeps generated dependency module maps and framework search-path response files in the project’s Derived/ directory with stable file mtimes when their contents have not changed, and stops rewriting them on every warm tuist generate. This avoids Xcode treating unchanged generated compiler inputs as changed build inputs, which previously forced unnecessary Swift recompilation in warm tuist test --build-only runs. The early Derived/ cleanup still preserves Derived/ModuleMaps and Derived/FrameworkSearchPaths so active compiler inputs survive regeneration, while stale *-deps.modulemap and *.resp files that are no longer active get cleaned up. External files such as Package.modulemap next to the generated files are preserved.