Generated dependency module maps keep stable mtimes across warm builds

Warm tuist test --build-only runs stay incremental again on stateful CI and local machines for projects whose Swift targets reference generated dependency module maps. Generated module maps keep stable mtimes when the bytes don’t change, and stale *-deps.modulemap / *.resp files are still cleaned up so they don’t pile up across generations.