Generated module map and response file mtimes are preserved across warm generations

tuist test –build-only on warm projects no longer invalidates Swift compilation every time generation runs. Generated dependency module maps under Derived/ModuleMaps and framework search path response files under Derived/FrameworkSearchPaths keep their modification time when the bytes are unchanged, so Xcode treats them as stable compiler inputs. Active generated files are still kept in place during the early Derived cleanup, while stale ones are pruned with targeted patterns so external SwiftPM module maps nearby are left alone.