Warm builds stop invalidating Swift compilation on unchanged module maps

Generated compiler inputs (dependency module maps and framework search path response files) keep stable modification times across warm tuist test –build-only runs when their contents have not changed, while stale generated files are still cleaned up. Stateful CI and local warm builds no longer re-Swift-compile projects for unchanged module map bytes.