Generated module maps stay incremental across warm builds

Warm tuist test --build-only runs no longer force Xcode to rebuild Swift files whose compiled content has not changed. Generated dependency module maps and framework search path response files keep stable mtimes across warm generation instead of being rewritten, while stale generated files in those directories are still cleaned up via a scoped pattern that leaves unrelated files (such as Package.modulemap) alone.